Method and apparatus for optimizing internet communications

ABSTRACT

An apparatus and a method by a terminal in a wireless communication system are provided. The method includes transmitting first information including a public land mobile network identifier (PLMN ID) for a sponsored service, to a first server operated by a service provider, receiving, in response to the first information, second information including a token related to the sponsored service from the first server, transmitting third information requesting the sponsored service based on the token to a second server operated by a network operator corresponding to the PLMN ID, and receiving authentication information from the second server.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of prior application Ser.No. 14/674,659, filed on Mar. 31, 2015, which will issue as U.S. Pat.No. 9,628,976 on Apr. 18, 2017, and claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Jun. 23, 2014 in theKorean Intellectual Property Office and assigned Serial number10-2014-0076798, of a Korean patent application filed on Aug. 13, 2014in the Korean Intellectual Property Office and assigned Serial number10-2014-0104963, of a Korean patent application filed on Aug. 21, 2014in the Korean Intellectual Property Office and assigned Serial number10-2014-0109232, and of a Korean patent application filed on Sep. 17,2014 in the Korean Intellectual Property Office and assigned Serialnumber 10-2014-0123867, the entire disclosure of each of which is herebyincorporated by reference.

TECHNICAL FIELD

The present disclosure relates to a method and an apparatus foroptimizing Internet communications. More particularly, the presentdisclosure relates to a method and an apparatus for effectivelyexchanging information between nodes in wireless communication systems,in order to optimize Internet communications.

BACKGROUND

In general, wireless communication systems have been developed toprovide voice services allowing for a user's mobility. The wirelesscommunication systems have been growing to encompass data services aswell as voice services, and they have considerably advanced to providehigh speed data services over recent years. However, the currentwireless communication systems have limitations, such as a lack ofresources, and insufficiency of high speed data services, so moreadvanced wireless communication systems are in demand.

In order to meet such demands, the 3rd Generation Partnership Project(3GPP) has standardized technology of the wireless communication system,based on various radio access networks (RAN) such as Evolved-UniversalMobile Telecommunications System (UNITS) Terrestrial Radio AccessNetwork (E-UTRAN)/UTRAN/Global System for Mobile Communications (GSM)Edge RAN (GERAN).

A 3GPP standard-based communication system may support various kinds ofservices and devices. For example, the 3GPP standard-based communicationsystem may support communication devices related to the Internet ofThings (IoT), in which people are not, or are seldom involved, as wellas typical communication devices, such as smart phones directly used bypeople. In addition, the 3GPP standard-based communication system mayprovide a device management service, and a communication service, bywhich specific information is transmitted to or received from devices,as well as voice services and multimedia services.

In the case of a multitude of devices that use the Internet of Things,short message service (SMS) messages and data, which are exchangedbetween the devices using the IoT, may increase. In this case, otherservices for the device may deteriorate due to the transaction of themessages.

The above information is presented as background information only toassist with an understanding of the present disclosure. No determinationhas been made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the present disclosure.

SUMMARY

Aspects of the present disclosure are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentdisclosure is to provide a method and an apparatus for optimizingInternet communication. More specifically, the present disclosureprovides a method and an apparatus for effectively exchanginginformation between nodes in a wireless communication system, in orderto optimize Internet communication.

Another aspect of the present disclosure is to provide a method and anapparatus for controlling to maintain the quality of various servicesprovided by the communication system, in which there are many devicesthat transmit and receive messages through communication providernetworks, and by which the complexity of the system increases due to thesame.

Another aspect of the present disclosure is to provide a method and anapparatus for preventing the quality of the Internet from deterioratingdue to the exchange of short message service (SMS) messages or data,when there are many devices that transmit and receive messages throughcommunication provider networks, thanks to the commercialization of theInternet of Things (IoT).

In accordance with an aspect of the present disclosure, a terminal in awireless communication system is provided. The terminal includes atransceiver configured to transmit and receive a signal, and acontroller configured to transmit first information including a publicland mobile network identifier (PLMN ID) for a sponsored service, to afirst server operated by a service provider, to receive, in response tothe first information, second information including a token related tothe sponsored service from the first server, to transmit thirdinformation requesting the sponsored service based on the token to asecond server operated by a network operator corresponding to the PLMNID, and to receive authentication information from the second server.

In accordance with another aspect of the present disclosure, a server ina wireless communication system is provided. The server includes atransceiver configured to transmit and receive a packet, and acontroller configured to store first information related to a tokenauthorized by the network operator and a service provider. The tokencorresponds to a public land mobile network identifier (PLMN ID) of thenetwork operator, to receive second information requesting a sponsoredservice from a terminal, to determine whether the terminal is authorizedto use the sponsored service based on the first information related tothe token and the second information requesting the sponsored service,and to transmit third information indicating whether the terminal isauthorized to use the sponsored service.

In accordance with another aspect of the present disclosure, a method bya terminal in a wireless communication system is provided. The methodincludes transmitting first information including a public land mobilenetwork identifier (PLMN ID) for a sponsored service, to a first serveroperated by a service provider, receiving, in response to the firstinformation, second information including a token related to thesponsored service from the first server, transmitting third informationrequesting the sponsored service based on the token to a second serveroperated by a network operator corresponding to the PLMN ID, andreceiving authentication information from the second server.

In accordance with another aspect of the present disclosure, a method bya server in a wireless communication system is provided. The methodincludes storing first information related to a token authorized by thenetwork operator and a service provider, wherein the token correspondsto a public land mobile network identifier (PLMN ID) of the networkoperator, receiving second information requesting a sponsored servicefrom a terminal, determining whether the terminal is authorized to usethe sponsored service based on the first information related to thetoken and the second information requesting the sponsored service, andtransmitting third information indicating whether the terminal isauthorized to use the sponsored service.

In addition, embodiments of the present disclosure may provide a methodand an apparatus for changing services, such as data charging of asponsored data service, or traffic, according to a contract between aservice provider and a communication network provider, and theactivities of a user.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, features, and advantages of certainembodiments of the present disclosure will be more apparent from thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a diagram illustrating a structure of a communication systemaccording to an embodiment of the present disclosure;

FIG. 2 illustrates an operation of user equipment (UE) and acommunication system for transmitting messages according to anembodiment of the present disclosure;

FIG. 3 illustrates an example for processing mobile terminating (MT)short message service (SMS) messages according to an embodiment of thepresent disclosure;

FIG. 4 illustrates an operation of user equipment and a network forprocessing mobile originating (MO) SMS messages according to anembodiment of the present disclosure;

FIG. 5 illustrates an operation of configuring a radio bearer (RB) fortransmitting user data through a control plane according to anembodiment of the present disclosure;

FIG. 6 illustrates an operation of user equipment and a network forprocessing MT SMS messages in a case of using a user data signalling RB(UDSRB) according to an embodiment of the present disclosure;

FIG. 7 illustrates an operation of user equipment and a network forprocessing MO SMS messages in a case of using a UDSRB according to anembodiment of the present disclosure;

FIG. 8 illustrates an operation of user equipment in a case where datatransmission/reception through a control plane is required without otherpacket switch (PS) data transmission/reception according to anembodiment of the present disclosure;

FIG. 9 illustrates an operation of releasing a radio resource control(RRC) connection when SMS transmission is completed according to anembodiment of the present disclosure;

FIG. 10 is a block diagram of communication equipment according to anembodiment of the present disclosure;

FIG. 11 is a block diagram of an evolved Node B (eNB) according to anembodiment of the present disclosure;

FIG. 12 is a block diagram of a mobility management entity (MME)according to an embodiment of the present disclosure;

FIG. 13 illustrates a network structure for providing a sponsored dataservice according to an embodiment of the present disclosure;

FIG. 14 illustrates a method for providing a sponsored data service to auser according to an embodiment of the present disclosure;

FIG. 15 illustrates a modification of FIG. 14 wherein a charging key isnot used according to an embodiment of the present disclosure;

FIG. 16 illustrates a method for additionally transferring an address ofa web service according to an embodiment of the present disclosure;

FIG. 17 illustrates a method for providing a conditional free sponsoreddata service according to an embodiment of the present disclosure;

FIG. 18 illustrates a method for changing a sponsored data serviceaccording to activities of a user according to an embodiment of thepresent disclosure;

FIG. 19 illustrates a method for transmitting connection information toa core network node by user equipment using protocol configurationoption (PCO);

FIG. 20 illustrates another method for transmitting connectioninformation to a core network node by user equipment using PCO accordingto an embodiment of the present disclosure;

FIG. 21 illustrates a method for calculating a volume of datatransmitted and received through a sponsored data service in the UE andinforming a user of the volume of data according to an embodiment of thepresent disclosure;

FIG. 22 illustrates an operation of a UE in a conditional sponsored dataservice according to an embodiment of the present disclosure;

FIG. 23 illustrates an operation of a UE in a conditional sponsored dataservice according to an embodiment of the present disclosure;

FIG. 24 illustrates a method by which a UE receives a sponsored dataservice information from a provider network for use according to anembodiment of the present disclosure;

FIG. 25 illustrates a method by which a UE receives information on asponsored data service in real time from a network for use according toan embodiment of the present disclosure; and

FIG. 26 illustrates an example of displaying features of a sponsoreddata services in a UE according to an embodiment of the presentdisclosure.

Throughout the drawings, it should be noted that like reference numbersare used to depict the same or similar elements, features, andstructures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the present disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein may be made without departing from the scope and spirit of thepresent disclosure. In addition, descriptions of well-known functionsand constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of the presentdisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of the presentdisclosure is provided for illustration purpose only and not for thepurpose of limiting the present disclosure as defined by the appendedclaims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

In describing the various embodiments of the present disclosure,descriptions related to technical contents which are well-known in theart to which the present disclosure pertains, and are not directlyassociated with the present disclosure, will be omitted. Such anomission of unnecessary descriptions is intended to prevent obscuring ofthe main idea of the present disclosure and more clearly transfer themain idea.

For the same reason, in the accompanying drawings, some elements may beexaggerated, omitted, or schematically illustrated. Further, the size ofeach element does not entirely reflect the actual size.

The advantages and features of the present disclosure and ways toachieve them will be apparent by making reference to various embodimentsas described below in detail in conjunction with the accompanyingdrawings. However, the present disclosure is not limited to theembodiments set forth below, but may be implemented in various differentforms. The following embodiments are provided only to completelydisclose the present disclosure and inform those skilled in the art ofthe scope of the present disclosure, and the present disclosure isdefined only by the scope of the appended claims.

It will be understood that each block of the flowchart illustrations,and combinations of blocks in the flowchart illustrations, may beimplemented by computer program instructions. These computer programinstructions may be provided to a processor of a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing the functionsspecified in the flowchart block or blocks. These computer programinstructions may also be stored in a computer usable orcomputer-readable memory that may direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstruction means that implement the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

And each block of the flowchart illustrations may represent a module,segment, or portion of code, which includes one or more executableinstructions for implementing the specified logical function(s). Itshould also be noted that in some alternative implementations, thefunctions noted in the blocks may occur out of the order. For example,two blocks shown in succession may in fact be executed substantiallyconcurrently or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved.

As used herein, the “unit” or “module” refers to a software element or ahardware element, such as a Field Programmable Gate Array (FPGA) or anApplication Specific Integrated Circuit (ASIC), which performs apredetermined function. However, the “unit” or “module” does not alwayshave a meaning limited to software or hardware. The “unit” or “module”may be constructed either to be stored in an addressable storage mediumor to execute one or more processors. Therefore, the “unit” or “module”includes, for example, software elements, object-oriented softwareelements, class elements or task elements, processes, functions,properties, procedures, sub-routines, segments of a program code,drivers, firmware, micro-codes, circuits, data, database, datastructures, tables, arrays, and parameters. The elements and functionsprovided by the “unit” or “module” may be either combined into a smallernumber of elements, “unit”, or “module” or divided into a larger numberof elements, “unit”, or “module”. Moreover, the elements and “units” or“modules” may be implemented to reproduce one or more central processingunits (CPUs) within a device or a security multimedia card.

In the following description of various embodiments of the presentdisclosure, a detailed description of known functions or configurationsincorporated herein will be omitted when it is determined that thedetailed description thereof may unnecessarily obscure the subjectmatter of the present disclosure.

Also, in a detailed description of various embodiments of the presentdisclosure, a basic 3^(rd) Generation Partnership Project (3GPP) LongTerm Evolution (LTE) system will be considered as a main subject.However, various embodiments of the present disclosure may be appliedeven to other communication/computer systems having a similar technicalbackground and a similar system form without significantly departingfrom the scope of the present disclosure. This applicability may bedetermined by those skilled in the art in the technical field of thepresent disclosure.

For example, the present technology directed to the LTE system may alsobe applied to the universal mobile telecommunications system (UMTS)terrestrial radio access network (UTRAN)/global system for mobilecommunications (GSM) edge RAN (GERAN) system having the similar systemarchitecture. With regard to this, evolved Node B (eNB) RAN node may bereplaced by radio network controller (RNC)/base station controller(BSC), serving gateway (S-GW) may be omitted or incorporated in servinggeneral packet radio service (GPRS) support node (SGSN), and packet datanetwork gateway (P-GW) may correspond to gateway GPRS support node(GGSN). Further, the concept of a bearer in the LTE system maycorrespond to a packet data protocol (PDP) context in the UTRAN/GERANsystem.

Although the various embodiments of the present will be described on theassumption that the main service is a short message service (SMS), it isobvious for those skilled in the art to understand that the variousembodiments of the present disclosure may be applied to other dataservices or message services, such as Internet protocol (IP)-based datacommunication services without departing from the scope of the presentdisclosure.

FIG. 1 is a diagram illustrating a structure of a communication systemaccording to an embodiment of the present disclosure. The communicationsystem may be a mobile communication system based on LTE according to anembodiment of the present disclosure.

Referring to FIG. 1, as shown in the drawing, a wireless access networkof an LTE mobile communication system is comprised of an eNB or anevolved UTRAN (EUTRAN) 130, a mobility management entity (MME) 120, andan S-GW 130.

User equipment (UE) 100 may connect with external networks through theeNB 110, the S-GW 130, and a P-GW 160. The UE may make a PDN connectionin order to transmit and receive data through the P-GW, and a single PDNconnection may include one or more Evolved Packet System (EPS) bearers.

An application function (AF) 140 is a device for exchanging informationrelated to applications with a user in the level of applications.

A policy charging and rules function (PCRF) 150 is a device forcontrolling a policy related to the quality of service (QoS) for theuser, and a policy and charging control (PCC) rule corresponding to thepolicy is transferred to the P-GW 160 to be thereby applied.

The eNB 110 is a RAN node and the eNB 110 corresponds to an RNC of anUTRAN system and a BSC of a GERAN system. The eNB 110 is connected withthe UE 100 through a wireless channel to play a role similar to thetypical RNC/BSC.

User traffic including real-time services, such as a voice over IP(VoIP) service through the IP, is served through a shared channel in theLTE system. Therefore, a device that collects status information on theUE 100 for scheduling is required, and the eNB 110 may operate as such adevice.

The S-GW 130 is a device for providing data bearers, and it may createand eliminate data bearers according to the control of the MME 120.

The MME 120 is a device for controlling various operations, and a singleMME 120 may be connected with a plurality of eNBs.

The policy charging and rules function (PCRF) 150 is an entity forcontrolling overall QoS and charging of traffic.

Although not shown in the drawing, the communication system structuremay include a mobile switching center (MSC), and a gateway mobileswitching center (GMSC). The GMSC plays a role of a gateway to acommunication provider network for circuit switched services, such as avoice service, or an SMS. The MSC is a device for controlling thecircuit-switching (CS) domain.

Hereinafter, a method and an apparatus for optimizing Internetcommunications, according to an embodiment of the present disclosure,will be described. Particularly, a method and an apparatus foreffectively exchanging information between nodes in a wirelesscommunication system to optimize Internet communications will bedescribed in the following embodiment. The following embodiment may beapplied to a communication method of communication devices that supportthe Internet of Things (IoT).

When there are many user devices that transmits and receives messagesthrough a communication provider network in a mobile communicationsystem (e.g., when the number of user devices that use the IoTincreases), or when the complexity of the system increases due to anincrease in the number of user devices, the quality of various servicesprovided by the communication system may be degraded. In order toaddress the problem above, the present embodiment will provide a methodand an apparatus to improve communication efficiency in spite ofdeterioration of the quality of services provided by a communicationsystem.

If the number of user devices that use a messaging service (e.g., anSMS) increases, other services (e.g., a voice service) may not beproperly provided due to processing the messaging service, so thequality thereof may deteriorate. Therefore, a method and an apparatusfor preventing the quality of other services for user equipment fromdeteriorating even with a multitude of user devices that use themessaging service, are required.

When the UE switches from an idle state to a connection state for themessaging service, it may be useless to configure the context for otherservices except for the messaging service. Accordingly, when the UE isprovided with only the messaging service, a method and an apparatus forselectively configuring the context only for the messaging service arerequired.

FIG. 2 illustrates an operation of UE and a communication system fortransmitting messages according to an embodiment of the presentdisclosure.

Referring to FIG. 2, a communication system according to the embodimentof the present disclosure may include UE 210, an eNB 220, an MME 230, anMSC 240, and a GMSC 250. Functions of the entities have been describedwith reference to FIG. 1 above.

The UE 210 has been attached to the communication provider network tothereby receive SMS messages at operation S201.

If the GMSC 250 receives a mobile terminating (MT) SMS message for theUE 210 from an external network, the GMSC 250 may forward the SMSmessage to the MSC 240 through, for example, a forward short message atoperation S211.

When the MSC 240 receives the SMS message from the GMSC 250, the MSC 240may transmit a message stating that a service for the UE has occurred,for example, a signalling gateway (SGs) service request message, to theMME 230 at operation S213.

The MME 230 may determine a paging operation according to connectionstatus of the UE 210. If the UE 210 is in an idle mode, the MME maytransfer a paging message to the eNB. If the UE 210 is in a connectionmode, the operations S221 to S226 may be omitted. If the UE 210 is inthe idle mode, the MME 230 may transmit a paging request message to theeNB at operation S221.

When the paging message is received from the MME 230, the eNB 220 maybegin the paging operation with the UE 210 at operation S222.

The UE that has received the paging message from the eNB may perform anoperation of random access and an operation of establishing an RRCconnection at operation S223.

The UE 210 may transmit an RRC connection setup completion message thatincludes a service request message during the establishment of the RRCconnection. The eNB 220 may forward the service request message receivedfrom the UE 210 to the MME 230 at operation S224.

The MME 230 may perform an operation of setting the context of the UE inthe eNB 220 at operation S225.

The eNB 230 may perform the establishment of a signaling radio bearer(SRB) and a data RB (DRB) with the UE, according to the UE contextreceived from the MME 230. In this operation, an SRB2 that is able totransmit a non-access stratum (NAS) message is established at operationS226.

The MME 230 may transmit a service request message, i.e., a messagerequesting for SMS transmission in the present embodiment, for example,an SGs service request message, to the MSC 240 at operation S231.

The MSC 240 may transmit the SMS message received from the GMSC 250 tothe MME 230, wherein the SMS message may be included in an SGs downlink(DL) unidata message at operation S233.

The MME 230 may transmit the SMS message received from the MSC 240 tothe UE 210 through the eNB 220. At this time, the MME 230 may includethe SMS message in the NAS message (e.g., DL NAS transport, or DLgeneric NAS transport) to be thereby transmitted, and the NAS message isincluded in a message, e.g., an S1 Application Protocol (S1AP) DL NAStransport message, which is forwarded to the eNB, to be therebytransferred at operation S235. The 3GPP has determined that the SMSmessage is to be transmitted using the NAS message, even though the SMSmessage is not a control message but user data.

The eNB 220 may transmit the DL NAS transport message received from theMME 230 to the UE 210 using SRB2 (a “DLinformation” transfer message) atoperation S237

The UE 210 may transmit an acknowledgement (ACK) message upon thereceipt of the SMS message, and the ACK message is forwarded to the MSC240 through the eNB 220, and the MME 230 in operations S241, S243 andS245. The UE 210 transmits the ACK message using SRB2 (an “uplink (UL)information” transfer message). The UE 210 may transmit ULInformation(Transfer—SIB 2) to the eNB 220 in operations S241. The eNB 220 maytransmit UL NAS transport to the MME 230 in operations S243. The MME 230may transmit UL Unidata to the MSC 240 in operations S245.

The UE 210 may transmit a delivery report stating that the received SMSmessage has been correctly stored, and the delivery report is forwardedto the GMSC 250 through the eNB 220, the MME 230, and the MSC 240 atoperations S251, S253, S255, and S257. The UE may transfer the deliveryreport using SRB2 (the “ULinformation” transfer message).

Afterwards, the UE 210 may receive an ACK message in response to thedelivery report through SRB2.

Although the operation of the UE and the network is described in thecase of the MT (i.e., reception of messages) SMS message for the UE inthe present embodiment, the operation of the UE and the network in thecase of a mobile originating (MO) (i.e., transmission of messages)message may be similar to the same. The case of the MO message isdifferent from the embodiment above in that the paging operation of theembodiment is not required, and the UE transmits an SMS message to theGMSC through the eNB, the MME, and the MSC. In addition, in the case ofthe MO message, the UE receives an ACK message in response to the SMSmessage from the GNSC, receives a delivery report of the SMS messagefrom the GMSC, and transmits an ACK message in response to the deliveryreport to the GMSC. The UE transmits the ACK message for the SMS messageor the delivery message using a UL message (“ULinformation” transfer/ULNAS transport), and receives the ACK message for the SMS message and thedelivery report using a DL message (“DLinformation” transfer/DL NAStransport).

In addition, in the present embodiment, in order to transmit one SMSmessage to the UE, the NAS message transmission (using SRB2) isperformed four times in total. Therefore, if the number of pieces of UEtransmitting and receiving SMS messages increases, transmission of NASmessages may become frequent. Accordingly, as the transmission of SMSmessages increases, the general NAS procedure (the TA update, the EPSsession management (ESM) procedure, and the like) using the same SRB2may be affected in operation thereof. Particularly, the devices usingthe IoT are more likely to use SMS messages as communication means, andin this case, frequent transmission and reception of SMS messages maydegrade the quality of other services.

In addition, if priority of resource allocation to the SRB2 in the eNBis higher than those to the DRBs, the SMS message that is a kind ofgeneral user data is transmitted through the SRB2, so this may cause adelay of transmission of control messages through the DRB. For example,when SMS and IP Multimedia Subsystem (IMS)-based services are supportedthrough the communication provider network and the number of SMSmessages to be processed by the eNB increases, the resource allocationof the DBR for transmitting control messages, for example, an invitesession initiation protocol (SIP) message for starting a voice call, ofthe IMS-based service may be delayed due to the resource allocation ofthe SRB2 for transmitting the SMS messages. In this case, the callconfiguration of a voice service, which is sensitive to the transmissiondelay, may be delayed due to the transmission of the SMS messages thatare not sensitive to the transmission delay. Likewise, when the resourceallocation for the DRB is delayed due to an increase in the number ofSMS messages to be processed by the eNB, the resource allocation to theongoing voice call (using an IMS media bearer) is not stable to therebylower the quality of the voice service.

Hereinafter, a method and an apparatus to address the problems abovewill be described through the various embodiments of the presentdisclosure.

The first embodiment suggests that if NAS message transmission (e.g.,message transmission through the SRB2) is carried out for user data, forexample, SMS messages, the priority of a logical channel (LC) for theSRB2 is lowered for a predetermined time. The priority may mean priorityof resource allocation to the LC, and resource scheduling for the LC maybe performed based on the priority. In order to indicate the priority,indication information or priority values may be used. For example, theLC given a low priority value may be allotted with the resource first.The priority may indicate the order of resource allocation to aplurality of LCs in the same UE. Moreover, the priority may indicate theorder of resource allocation to a plurality of LCs in a plurality ofpieces of UE in the eNB. The priority set forth above may be applied tothe embodiments of FIGS. 3 to 12.

Although typically, the NAS messages have not been separated accordingto a type, in the embodiment of the present disclosure, the NAS messagesmay be divided into NAS messages for user data (e.g., data for SMSmessages), and general NAS messages. In addition, in the case of NASmessage transmission for user data, the priority of the LC for the samemay be adjusted. That is, the priority of the LC for the SRB2 may beconfigured to be lower than that of the LC for the general NAS messageor the DRB for a predetermined time. The priority may correspond to theorder of scheduling. In addition, a timer may be additionally adopted toset the time for adjusting the priority. This enables the other SRB2(e.g., NAS procedure) or the DRB (e.g., IMS signaling, or mediatransmission) to be allotted with the resource, or prevents the delay ofthe resource allocation to the same, even with the occurrence of SRB2transmission for user data.

FIG. 3 illustrates an example for processing MT SMS messages accordingto an embodiment of the present disclosure.

Referring to FIG. 3, operations S301 to S333 of FIG. 3 are the same asoperations S201 to S233 of FIG. 2, so the detailed description thereofwill be omitted here.

The MME 330 may include information on the type of NAS message to betransmitted, i.e., information stating that the NAS message to betransmitted includes not the general EPS mobile management (EMM) or ESMmessage but the SMS message (or user data, or messages), in a message tobe sent to the eNB 320 for SMS transmission, e.g., a DL NAS transportmessage at operation S335. The information may be configured asinformation showing transition priority of the NAS message includinguser information rather than information indicating the type of NASmessage as describe above. In addition, the message may further includea timer. After transmitting the SMS message (user data, or messages),the eNB transmits message related to the SMS message using the SRB2. Indoing so, the timer refers to a value corresponding to a specific amountof time for which the priority of scheduling for the LC of the SRB2 istemporarily lowered.

The eNB 320 may recognize information on the type of NAS message orpriority information from the DL NAS transport message received from theMME, and based thereon, may adjust the priority of the LC correspondingto a bearer for transmitting the NAS message at operation S341. If thetype of NAS message is configured as not the EMM or ESM message but theSMS message (user data, or messages), or the transition priority of theNAS message is configured to be low, in an S1-AP message, e.g., a DLtransport message, received from the MME 330, the eNB 320 may lower thepriority of scheduling (resource allocation) of the LC for the SRB2 usedin transmitting the corresponding NAS message for a predetermined periodof time. In addition, if the DL transport message, for example, theS1_AP message, includes a timer value, the eNB 320 may trigger thetimer, and may maintain the low priority of scheduling of the LC for theSRB2 until the configured timer expires. The lowering of the priority ofscheduling of the LC for the SRB2 may be applied to the case where theUE 310 requests resource allocation of the LC for the SRB2 fortransmitting a UL NAS message, as well as the case of transmitting theDL NAS message. Although the eNB 320 receives the timer information fromthe MME in the present embodiment, the eNB 320 may have its own timer tobe configured and triggered. For example, as a result of analyzing thereceived DL NAS transport message, if the NAS message relates to userdata, or information instructing to lower the priority of the NASmessage is included therein, the eNB 320 may configure and trigger thetimer.

The eNB 320 may transfer the NAS message received from the MME 330 tothe UE 310, based on the configured priority at operation S343. The UE310 may transmit a UL NAS message in response to the NAS messagereceived from the eNB 320 at operation S351. The priority of the LC andthe configuration of the timer may be applied to resource allocation ofthe LC for the SRB2 in the case of UL transition of the UE 310 as well.

FIG. 4 illustrates an operation of UE and a network for processing MOSMS messages according to an embodiment of the present disclosure.

Referring to FIG. 4, a UE 410 has been attached to the communicationprovider network to thereby transmit and receive data at operation S401.

The UE 410 may trigger an MO SMS message at operation S411.

If the UE 410 is in an idle state, the UE 410 may perform establishmentof an RRC connection for SMS transmission at operation S413.

The UE 410 may transmit a service request message to an MME 430 throughan eNB 430. The message is contained in an RRC setup completion messageto be thereby transmitted to the eNB 420, and the eNB may forward thesame to the MME 430 at operation S415.

The MME 430 may perform setting the context of the UE in the eNB 420.

The eNB 420 may perform establishment of an SRB and a DRB with the UE410 in operation S419, according to the UE context received from the MMEat operation S417. This is the operation of RRC connectionreconfiguration.

After the setup of SRB2 is completed, the UE 410 may transmit a resourceallocation request message, i.e., a scheduling request (SR) message, ora buffer status request (BSR) message for transmitting a message throughthe UL at operation S421. The message may include information on thetype of NAS message to be transmitted, i.e., information stating thatthe NAS message to be transmitted includes not the general EMM or ESMmessage but the SMS message (user data, or messages). The informationmay be configured as information showing the transition priority of theNAS message rather than the information indicating the type of NASmessage as describe above. In addition, the message may further includea timer. After transmitting the SMS message (user data, or messages),the eNB transmits message related to the SMS message using the SRB2. Indoing so, the timer refers to a value corresponding to a specific amountof time for which the priority of scheduling for the LC of the SRB2 istemporarily lowered.

The eNB 420 may recognize that resource allocation to the SRB2 isrequired, but eNB 420 may recognize information on the type or thepriority, based on the SR message or the BSR message received from theUE 410. If the type of information included in the scheduling requestmessage of the UE 410 is configured not as the general EMM or ESMmessage but the SMS message (user data, or messages), or the transitionpriority of the NAS message is configured to be low, the eNB 320 maytemporarily lower the priority of scheduling (resource allocation) ofthe LC for the SRB2 used in transmitting the corresponding NAS message.For example, the scheduling may be configured to be later than the LCfor other bearers. In addition, if the S1_AP message, for example, theDL NAS transport message, includes a timer value, the timer may betriggered, the low priority of scheduling of the LC for the SRB2 may bemaintained until the configured timer expires. The eNB 420 may configureand trigger the timer without receiving the timer information from theUE 410.

The eNB 420 may inform the UE of the UL grant according to thescheduling result at operation S425.

The UE 410 may transmit an NAS message including an SMS message usingthe UL resource allotted by the eNB 420 at operation S431. The messageis included in an RRC information transfer message to be therebytransferred to the eNB 420. The eNB 420 may extract the NAS message fromthe RRC message received from the UE 410 to thereby forward the same tothe MME 430 at operation S433, and the MME 430 may extract the SMSmessage from the NAS message to thereby forward the same to an MSC 440at operation S435. Finally, the SMS message may be forwarded from theMSC 440 to a GSMC 450 at operation S437.

In transmitting the SMS message, the SRB2 is still used, but thepriority thereof is temporarily lowered in the embodiment above. Thatis, considering that the UE transmits the SMS message using the NASmessage, the priority of the LC for the SRB2 is adjusted upon therequest for resource allocation to the LC for the SRB2. In addition touse of the SRB2, in the embodiment of the present disclosure, the UE maymake a request to the eNB for resource allocation to the LC for otherDRBs rather than the SRB2, and may transmit the NAS message includingthe SMS message using a UL resource allotted by the eNB.

Hereinafter, a method according to the second embodiment of the presentdisclosure in order to address the problem above will be described. Inthe present embodiment, a new type of RB is introduced to transmit orreceive user data, such as SMS messages, through a control plane, sothat the transmission quality of a general control plane message (i.e.,EMM/ESM NAS messages), or the DRB that should be given a high priority,is prevented from deteriorating due to the user data, such as the SMSmessage, which is transmitted or received through the control plane.

FIG. 5 illustrates an operation of configuring an RB for transmittinguser data through a control plane according to an embodiment of thepresent disclosure. In the present description, the RB for transmittinguser data through the control plane (NAS) is defined as a UDSRB forconvenience of explanation, but it may be defined in another name suchas SRB3.

Referring to FIG. 5, a UE 510 may perform an operation of RRC connectionestablishment for attaching thereof or TA updating at operation S501.

The UE 510 may transmit to an RRC setup completion message, an attachingmessage, or a TAU request message to an MME 530 through an eNB 520 atoperation S503. The UE 510 may include information showing support ofthe UDSRB of the UE 510 or a request for support thereof in the RRCsetup completion message, the attaching message, or the TAU requestmessage.

The MME 530 may transmit an update location message for the UE 510 to ahome subscriber server (HSS) 560 at operation S507. The MME 530 mayinclude information showing whether or not the current network supportsthe UDSRB in the update location message for the UE 510, which istransmitted to the HSS 560. The information may be included in the casewhere information stating the UE 510 supports the UDSRB is received, ora request for supporting the UDSRB is received from the UE 510.

The HSS 560 may transmit an update location ACK message includingsubscription information of the UE 510 to the MME 530 at operation S509.If the UE is able to support the UDSRB or the UE has subscribed to aservice using the UDSRB, the HSS 560 may include information showingthat the UE supports the UDSRB in the subscription information (includedin the update location ACK message) sent to the MME 530. In addition,the HSS 560 may forward basic QoS information (e.g., priority ofresource allocation, charging information, and the like) of the UDSRBtogether with the information above to the MME 530.

The MME 530 may determine whether or not the UDSRB is to be applied tothe UE 510 at operation S511. In doing so, the MME 530 may consider thesupport information of the UDSRB received from the UE 510, and thesubscription information (UDSRB support information) received from theHSS.

Although the UE 510 transmits the support information of the UDSRB orthe information including the UDSRB request to the MME in the presentembodiment, the information above may not be included in the “Attach/TAUrequest” operation. In this case, the MME 530 may determine whether ornot the UDSRB is to be applied, based on the subscription informationreceived from the HSS 560.

When the MME 530 determines that the UDSRB is to be applied to the UE510, the MME 530 may include information stating that the UDSRB isapplied in a message when setting the UE context in the eNB 520 atoperation S521. To this end, an S1_AP message. e.g., an initial UEcontext setup message, transmitted from the MME 530 to the eNB 520, mayinclude information stating that the UDSRB is supported. In addition,when the MME 530 determines that the UDSRB is to be applied to the UE510, the message may further include QoS information, for example,priority information for resource allocation, which is applied to theUDSRB as well as the information above.

When the UDSRB is to be applied to the UE 510, the eNB 520 may configurethe UDSRB according to the UE context received from the MME 530 atoperation S531. The configuration of the UDSRB includes creation of LCinformation for the UDSRB. That is, the bearer context of the UDSRB isconfigured between the MME and the UE, and the configuration of theUDSRB bearer includes creation of LC information corresponding to theUDSRB between the UE and the eNB.

In the case of applying the UDSRB to the UE 510, the eNB 520 maytransfer information for configuring the UDSRB to the UE 510 atoperation S541. At this time, the UDSRB information may be transmittedthrough an RRC connection reconfiguration message. For example,“SRB-ToAddMod” field of “RadioResourceConfigDedicated IE” in the RRCconnection reconfiguration message may be utilized. At this time, thepriority of the LC for the UDSRB may be designated in“LogicalChannelConfig” field included in the “SRB-ToAddMod”, wherein thepriority of the UDSRB may be configured to be lower those of other SRBs.In addition, the priority of the UDSRB may be configured to be lowerthan the LC of the DRB that is supposed to have a high priority, e.g.,the DRB that uses QoS class identifier (QCI) 1 or QCI 5.

The UE 510 having received the UDSRB configuration information from theeNB 520, may create an UDSRB according to the configuration information.Afterwards, the SMS messages may be transmitted through a control planeusing the UDSRB.

Although the UE transmits the information stating that the UDSRB issupported or the information on the request for the UDSRB to the corenetwork (MME) through the NAS message in the present embodiment, suchinformation may be transferred to the core network through the eNB usingthe RRC message. In this case, the UE may transfer the information inthe form of UE radio capability or feature group indicator (FGI) in theprocess of RRC connection establishment or UE radio capability enquiry.If the eNB receives the information from the UE, the eNB may forward thesame to the MME. At this time, an S1-AP message, e.g., an initial UEcontext setup response message or a UE radio capability match responsemessage may be used.

FIG. 6 illustrates the operation of a UE and a network for processing MTSMS messages in a case of using a UDSRB according to an embodiment ofthe present disclosure.

Referring to FIG. 6, operations S601 to S633 of FIG. 6 are the same asoperations S201 to S233 of FIG. 2, so the detailed description thereofwill be omitted here.

The MME 630 may transmit a message to the eNB 620 for SMS transmissionat operation S641. The message may be, for example, a DL NAS transportmessage. The MME 630 may include information on the type of NAS messageto be transmitted, i.e., information stating that the NAS message to betransmitted includes not the general EMM or ESM message but the SMSmessage (user data, or messages), in the message to be sent to the eNB620. The information may be configured as information showing thetransition priority of the NAS message rather than informationindicating the type of NAS message as describe above.

The eNB 620 may forward the NAS message received from the MME 630 to theUE 610. If the type of NAS message is configured as not the EMM or ESMmessage but the SMS message (user data, or messages), or the transitionpriority of the NAS message is configured to be low, in an S1-APmessage, e.g., a DL transport message, received from the MME 630, theeNB should use the UDSRB rather than the SRB2 when transmitting thecorresponding NAS message. At this time, the eNB may apply thescheduling (resource allocation) of the LC for the UDSRB according tothe UDSRB context at operation S643.

The eNB 620 may transmit the NAS message (including SMS messages)received from the MME 630 to the UE 610 using the allotted resource atoperation S645. At this time, the RRC message used for the same (e.g.,the “DLDataTransfer” message) may be transmitted using the UDSRB ratherthan the SRB2.

In the case where the UE 610 is to transmit packet data for a response(ACK) message to the received SMS message or a delivery report, the UE610 may request resource allocation by transmitting an SR message or aBSR message of the LC for the UDSRB in operation S647.

The eNB 620, as set forth above, may allot the UL grant to the UE byapplying the scheduling of the LC for the UDSRB at operation S651.

FIG. 7 illustrates an operation of UE and a network for processing MOSMS messages in a case of using a UDSRB according to an embodiment ofthe present disclosure.

Referring to FIG. 7, operations S701 to S717 of FIG. 7 are similar tooperations S401 to S417 of FIG. 4, so the detailed description thereofwill be omitted here.

In operation S719, an eNB 720 may transmit information for UDSRBconfiguration to a UE 710. This operation is similar to operation S541of FIG. 5. At this time, the information for UDSRB configuration may betransferred through the RRC connection reconfiguration message. Inaddition, the priority of the UDSRB may be configured to be lower thanthe LC of the DRB that is supposed to have a high priority, for example,the DRB that uses QCI 1 or QCI 5. After the UDSRB configuration iscompleted, the UE 710 may transmit a resource allocation requestmessage, i.e., a scheduling request message, or a buffer status requestmessage for transmitting the message through the UL at operation S721.The request message relates to the SMS message (or data transmittedthrough the control plane) of the UE, so the message corresponds to theLC of the UDSRB rather than the SRB2. That is, the LC of the SR or theBSR should be configured as the UDSRB.

The eNB 720 recognizes that resource allocation to the UDSRB isrequired, and may perform scheduling according to information (e.g.,priority) on the LC for the UDSRB. As a result of the scheduling, theUDSRB may not be prioritized for the resource allocation, compared tothe LC of SRB0/1/2 or the DRB of a high priority (e.g., the DRB of thebearer of QCI 1 or QCI 5) at operation S723.

The eNB 720 may inform the UE 710 of the UL grant according to theresult of scheduling in operation S725.

The UE 710 may transmit an NAS message including an SMS message usingthe UL resource allotted by the eNB 720 at operation S731. This messageis included in an RRC message, for example, a UL data transfer message,to be thereby forwarded to the eNB 720. The eNB 720 may extract the NASmessage from the RRC message received from the UE 710 to thereby forwardthe same to the MME 730 at operation S733, and the MME 730 may extractthe SMS message from the NAS message to thereby forward the same to theMSC 740 at operation S735. Finally, the SMS message may be transferredfrom the MSC 740 to the GSMC 750 at operation S737.

In the case of using the UDSRB as described above, the UE may transmitand receive data using a user plane (using the DRB), or using a controlplane (using the UDSRB). In the case where data transmission/receptionof the UE only through the control plane is required, information on theDRB does not need to be configured in the course of setting the contextof the UE. That is, in the case of transmitting and receiving the datausing only the UDSRB, the operation of configuring the DRB may beomitted to thereby reduce the number of exchanged messages and the sizeof the message. The third embodiment of the present disclosure will bedescribed with reference to FIG. 8 below.

FIG. 8 illustrates an operation of a user device in a case where datatransmission/reception though only a control plane is required withoutother PS data transmission/reception according to an embodiment of thepresent disclosure.

Referring to FIG. 8, operations S801 to S813 are similar to operationsS201 to S213 of FIG. 2 as are a MSC 840 and GMSC 850 similar to MSC 240and GMSC 250, so the detailed description thereof will be omitted.

If an MT SMS message (or data transmitted through the control plane) fora UE 810 occurs, an MME 830 may transmit data information transmittedthrough the control plane, or information on NAS user data to an eNB 820during the paging operation at operation S821.

The eNB 820 may recognize the occurrence of the paging for the MT SMSmessage (or data transmitted through the control plane), based on theinformation received from the MME 820, and may include data informationtransmitted through the control plane, for example, information on NASuser data, in the paging message to thereby transmit the same to the UE.

The UE 810 may recognize that the SMS message or data is to be receivedthrough the control plane, based on the message received in operationS823. In this case, the UE 810 may determine whether or not there isgeneral data to be transmitted and received through the user plane (DRB)at operation S831. Based on the determination result, the UE 810 maydetermine whether or not only the UDSRB is to be used. In addition, thecreation of the DRB may be omitted.

When it is determined that there is no data to be transmitted andreceived through the user plane, the UE may perform operations S833 toS853 in order to receive data. When the MO data to be transmitted andreceived through the control plane occurs in the UE, the UE maydetermine whether or not there is general data to be transmitted andreceived through the user plane (DRB), and if it is determined thatthere is no data to be transmitted and received, the UE may performoperations S833 to S853 as described below, in order to receive thedata.

The UE 810 may inform the eNB that an RRC connection needs to beestablished because of data transmission and reception through thecontrol plane, in establishing the RRC connection at operation S833.This may be made by configuring the establishment cause of the RRCconnection request message as “mo-NAS-userdata” (in the case oftransmission), or “mt-NAS-userdata” (in the case of reception).

The eNB 820 may identify that the UE 810 wishes to establish the RRCconnection because of data transmission and reception through thecontrol plane, based on information received from the UE 810.Accordingly, the eNB may figure out that configuration of the contextfor the UDSRB is required, whereas configuration of the context forother DRBs is not required at operation S835.

The eNB 820 and the UE 810 may establish the RRC connection throughoperations S837 and S839.

After the establishment of the RRC connection, the eNB 820 may transferan initial UE message to the MME 830 at operation S841. The informationstating that the UE 810 makes establishment of the RRC connectionbecause of data transmission/reception through the control plane may betransmitted when forwarding an initial UE message. For example, the UE820 may transfer RRC establishment cause (“mo-NAS-userdata,” or“mt-NAS-userdata”) together. According to this, the MME 830 may figureout that configuration of the context for the UDSRB is required withrespect to the UE, whereas configuration of the context for other DRBsis not required.

The UE 810 may include information stating that a datatransmission/reception service through the control plane is requested inthe initial UE message, e.g., the service request message, and maytransmit the same. According to this, the MME 830 may figure out thatconfiguration of the context for the UDSRB is required with respect tothe UE 810, whereas configuration of the context for other DRBs is notrequired.

When the MME 830 recognizes that a data transmission/reception servicethrough the control plane is requested by the UE, the MME 830 maydetermine whether or not the UDSRB may be used, that is, whether or notthere is available context of the UDSRB for the UE at operation S843.When it is determined that the UDSRB is available for the UE andconfiguration of the context for other DRBs is unnecessary, the MME 830may transmit a request message for setting the UE context to the eNB 820at operation S845. For example, only the context of the SRB and theUDSRB may be included in the initial UE context setup request message tobe thereby transmitted. Alternatively, the MME 830 may includeinformation stating that only the SRB and the UDSRB are to be used forthe UE in the message to be thereby transferred. In addition to theinformation, the MME 830 may further include QoS information to beapplied to the UDSRB, for example, the resource allocation priority, inthe message.

In the case of applying the UDSRB to the UE 810, the eNB 820 mayconfigure the UDSRB according to the UE context received from the MME830. The configuration of the UDSRB may include creation of LCinformation for the UDSRB. If the message received from the MME does notcontain the context information of the DRB, or contains informationstating that only the UDSRB and the SRB are to be used, the eNB mayconfigure the SRB and the UDSRB without configuration of the DRB.

In the case of applying the UDSRB to the UE 810, the eNB 820 maytransfer information for configuring the UDSRB to the UE 810 atoperation S847. At this time, the UDSRB information may be transmittedthrough an RRC connection reconfiguration message. More specifically,“SRB-ToAddMod” field of “Radio Resource Config Dedicated IE” in the RRCconnection reconfiguration message may be utilized. At this time, thepriority of the LC for the UDSRB may be designated in“LogicalChannelConfig” field included in the “SRB-ToAddMod”, wherein thepriority of the UDSRB may be configured to be lower those of other SRBs.In addition, the priority of the UDSRB may be configured to be lowerthan the LC of the DRB that is supposed to have a high priority, e.g.,the DRB that uses QCI 1 or QCI 5. In addition, the eNB 820 mayinformation on the SRB in the message to be thereby transmitted.

The UE 810 having received the configuration information on the UDSRBand the SRB from the eNB 820, may create an UDSRB according to theconfiguration information. Afterwards, the SMS messages transmittedthrough the control plane may be transmitted using the UDSRB.

The eNB 820 may transmit a message to the MME 830 to inform that thesetting of the context for the UE has been completed at operation S849.For example, the eNB 820 may inform the MME 830 of the completion of thecontext setup through an initial UE context setup completion messagethat may include information stating that the configuration has beencompleted using only the UDSRB and the SRB.

The MME 830 may determine whether or not creation/renewal of a SGW and ageneral packet radio service (GPRS) tunnelling protocol (GTP) tunnel isto be performed, based on the context setup completion message receivedfrom the eNB. In the case where only the UDSRB and the SRB areconfigured in the UE 810, the MME 830 does not perform thecreation/renewal of the SGW and the GTP tunnel at operation S851. Thatis, the MME 830 may not perform an operation of transmitting a modifybearer request message.

The configuration of the UDSRB was described in the third embodiment ofthe present disclosure. However, the embodiment of the presentdisclosure may be applied to SMS messages using the SRB2 as shown in thefirst embodiment as well as the UDSRB configuration. That is, the SMSmessage or data may be transmitted or received using the SRB2 withoutconfiguration of the UDSRB that is a separate bearer for transmittingthe SMS message or the user data through the control plane. In thiscase, likewise, when the DRB for transmitting and receiving general datadoes not need to be configured, only the SRB2 and the SRB may beconfigured. At this time, the configuration of the DRB may be omitted.

Since the SMS message has a predetermined message transmission pattern(i.e., SMS-ACK-Delivery Report-ACK transmission/reception) as mentionedabove, the UE and the eNB may know when the transaction of the SMSmessage terminates. When the transaction of the SMS message is finished,the RRC connection with the UE may be disconnected to thereby reduceunnecessary battery consumption and prevent waste of available resourcesof the eNB. The fourth embodiment of the present disclosure will bedescribed with reference to FIG. 9 below.

FIG. 9 illustrates an operation of releasing an RRC connection whentransmission of an SMS message is completed according to an embodimentof the present disclosure.

Referring to FIG. 9, in the present embodiment, a UE 910 and the networkmay transmit and receive data only through the control plane (i.e., theSRB and the UDSRB have been configured without configuration of theDRB), as described in the embodiment above at operation S901.

When the UE determines that transaction of the SMS message has beencompleted at operation S911, the UE may transmit an RRC connectionrelease request to the eNB at operation S913. At this time, the UE 910may further include information stating that there are no moreactivities of the UE, or data transmission has been terminated, in therequest.

The MME may determine completion of the transaction of the SMS message.If the MME 930 determines that the transaction of the SMS message hasbeen completed at operation S921, the MME 930 may transmit a UE contextrelease request to an eNB 920 at operation S923. At this time, a MME 930may further include information stating that there are no moreactivities of the UE 910, or data transmission has been terminated, inthe request.

The eNB may recognize that the UE 910 may be disconnected through atleast one of two processes above (informing by the UE, or informing bythe MME). The eNB 920 that has recognized that the UE 910 may bedisconnected, may release the signaling connection and all of resourcesfor the UE 910 at operation S931. In addition, the eNB may transmit anRRC connection release message to the UE in order to disconnect the RRCconnection with the UE.

Although the RRC connection release of the UE is requested based on thecompletion of the SMS message in the present embodiment, the UE may makea request for the RRC connection release in other cases, for example, inthe case where the UE identifies that general data transmission andreception using the DRB has been completed.

In the embodiment above, the UE may make a request for the RRCconnection release using an UE assistant information message. Thismessage may include information on preferable power configuration of theUE, which has been turned to be in a low power consumption, informationshowing that activities of the user have been finished(“endofuserActivity”), an RRC connection release request, and the like.When the eNB receives the UE assistant information message including theinformation above from the UE, the eNB may release the RRC connection ofthe UE.

In addition, the UE may transmit the RRC connection release requestmessage not to the eNB but to the MME. In this case, the UE may transmitthe NAS message including information stating that the RRC connectionneed to be released or the activities of the user have been completed,to the MME. The MME having received the message may transmit aninstruction for releasing the S1 or UE context to the eNB.

FIG. 10 is a block diagram of communication UE according to anembodiment of the present disclosure.

Referring to FIG. 10, a UE 1000 may include a transmitting/receivingunit 1010, a memory 1020, and a controller 1030. Thetransmitting/receiving unit 1010 may communicate with at least onenetwork node. The memory 1020 may store information and various programsfor operating the UE 1000. The controller 1030 may control overalloperations of the UE 1000. The controller 1030 may control the operationof the UE according to the first to the fourth embodiments of thepresent disclosure.

According to an embodiment of the present disclosure, the controller1030 may control to transmit an attaching request message includingUDSRB request information, or a TAU resource message, to receive theUDSRB configuration information from the eNB, to create an UDSRB, basedon the UDSRB configuration information, and to receive user data throughthe control plane using the created UDSRB. At this time, the UDSRB maybe an RB for transmitting and receiving the user data through thecontrol plane.

In addition, the controller 1030 may control to establish a logicalchannel (LC) between the UE corresponding to the UDSRB and the eNB whencreating the UDSRB. In addition, the controller may control to receiveinformation on scheduling of wireless resources for the UDSRB from theeNB, and the priority of the UDSRB for scheduling may be configured tobe lower than those of other SRBs or DRBs having QCI values in apredetermined range.

In addition, the controller 1030 may determine whether or not there isdata to be transmitted or received through the user plane. If there isno data to be transmitted or received through the user plane, thecontroller 1030 may transmit the RRC connection request message fortransmitting and receiving the user data using the control plane, andmay control to omit the configuration of the DRB, in response to the RRCconnection request message.

In addition, the controller 1030 may determine whether or not thetransaction of the user data using the UDSRB is completed, and if it isdetermined to be completed, the controller 1030 may control to transmitthe RRC connection release message to the eNB to thereby release the RRCconnection with the eNB.

Although the UE 1000 is divided into blocks in configuration andfunctions in the present embodiment for convenience of explanation, thepresent disclosure is not limited thereto. In addition, the UE 1000 mayperform the operation of the UE described in FIGS. 2 to 9 as well as theoperation of FIG. 10.

In addition, the controller 1030 of the UE may control the UE to performthe operation described in the various embodiments as shown in FIGS. 13to 26.

In addition, the controller 1030 may transmit first informationincluding a public land mobile network identifier (PLMN ID) for asponsored service, to a first server operated by a service provider,receive, in response to the first information, second informationincluding a token related to the sponsored service from the firstserver, transmit third information requesting the sponsored servicebased on the token to a second server operated by a network operatorcorresponding to the PLMN ID and receive authentication information fromthe second server.

In addition, the controller 1030 may configure a packet filter for thesponsored service and identify volume of packet transmission andreception for the sponsored service based on the packet filter.

In addition, the controller 1030 may display information of thesponsored service based on the identified volume of packet transmissionand reception for the sponsored service. The token includes at least oneof information on allowed volume of packet transmission and receptionfor the sponsored service and information on allowed time of thesponsored service. Also, the display information includes at least oneof information on remaining volume of packet transmission and receptionfor the sponsored service based on the information on allowed volume andthe identified volume and information on remaining time of the sponsoredservice based on the information on allowed time.

In addition, the controller 1030 may display at least two applicationsrelated to each of at least two sponsored services. The applicationincludes status information corresponding to the each of the sponsoredservice.

The sponsored service is a specific service that the service providerpays charge of a traffic between the terminal and the service providerto the network operator.

FIG. 11 is a block diagram of an eNB according to an embodiment of thepresent disclosure.

Referring to FIG. 11, an eNB 1100 may include a wired/wirelesscommunication unit 1110, a memory 1120, and a controller 1130. Thewired/wireless communication unit 1110 may communicate with at least oneof the network nodes. The memory 1120 may store information and variousprograms for operating the eNB 1100. The controller 1130 may controloverall operations of the eNB 1100. The controller 1130 may control theoperation of the eNB according to the first to the fourth embodiments ofthe present disclosure.

According to an embodiment of the present disclosure, the controller1130 may control to forward the attaching request message or the TAUresource message received from the UE to the MME, and to receive the UEcontext setup message including information indicating the support ofthe UDSRB for the UE, from the MME. In addition, the controller 1130 maycontrol to configure the UDSRB in the UE, based on the UE context setupmessage, and to transmit and receive user data using the set UDSRB. Atthis time, the UDSRB may be an RB for transmitting and receiving theuser data through the control plane.

In addition, the controller 1130 may control to establish a logicalchannel (LC) between the UE corresponding to the UDSRB and the eNB whencreating the UDSRB.

In addition, the controller 1130 may control scheduling of wirelessresources for the UDSRB in the UE, and the priority of the UDSRB forscheduling may be configured to be lower than those of other SRBs orDRBs having QCI values in a predetermined range.

Although the eNB 1100 is divided into blocks in configuration andfunctions in the present description for convenience of explanation, thepresent disclosure is not limited thereto. In addition, the eNB 1100 mayperform the operation of the eNB described in FIGS. 2 to 9 as well asthe operation of FIG. 11.

In addition, the controller 1130 of the eNB may support the UE tocommunicate with an upper layer node in the various embodiments as shownin FIGS. 13 to 26.

FIG. 12 is a block diagram of an MME according to an embodiment of thepresent disclosure.

Referring to FIG. 12, an MME 1200 may include a communication unit 1210,a memory 1220, and a controller 1230. The communication unit 1210 maycommunicate with at least one of network nodes. The memory 1220 maystore information and various programs for operating the MME 1200. Thecontroller 1230 may control overall operations of the UE 1000. Thecontroller 1030 may control the operation of the MME 1200 according tothe first to the fourth embodiments of the present disclosure.

According to an embodiment of the present disclosure, the controller1230 may control to receive the attaching request message, or the TAUresource message from the UE, and to transmit the location area updatemessage to the HSS, based on the request message. In addition, thecontroller 1230 may control to receive subscriber information includingthe UDSRB support indication information of the UE from the HSS, and todetermine the application of the UDSRB to the UE, based on thesubscriber information. At this time, the UDSRB may be an RB fortransmitting and receiving the user data through the control plane.

In addition, the controller 1230 may control to determine whether or notthe UDSRB is applied to the UE, based on UDSRB request informationincluded in the attaching message or the TAU request message and UDSRBsupport indication information of the subscriber information. Inaddition, when the UDSRB is determined to be applied, the controller1230 may control to transmit the UE context setup message including theUDSRB support indication information, to the eNB.

In addition, the controller 1230 may determine whether or not there isdata to be transmitted or received through the user plane for the UE. Ifthere is no data to be transmitted or received through the user plane,the controller 1230 may control to transmit information stating thatconfiguration of the DRB is not required.

Although the MME 1200 is divided into blocks in configuration andfunctions in the present description for convenience of explanation, thepresent disclosure is not limited thereto. In addition, the MME 1200 mayperform the operation of the MME described in FIGS. 2, 3, 4, 5, 6, 7, 8,and 9, 19, and 20 as well as the operation of FIG. 12.

Although the various embodiments of the present disclosure have beendescribed with reference to the drawings for convenience of explanation,the various embodiments may be performed independently, or by acombination thereof.

Although the GMSC and the MSC of a communication provider network areincluded the transmission path for SMS messages in the presentspecification and drawings for convenience of explanation and generalunderstanding of the disclosure, the present disclosure is not limitedthereto. The transmission path for SMS messages may include othernetwork entities. For example, in the case of using T4/T5 interfaces,the MT SMS message may be transferred to an MTC-IWF through anSMS-SC/GMSC/IWMSC, and the MTC-IWF may forward the same to the MME.

A network provider may make an agreement with the third party (orservice providers) to provide various services. For example, the networkprovider and the third party may make a sponsorship contract with eachother to thereby provide a sponsored data or charging service by whichthe third party provides services in the communication provider network,and the third party pays for a traffic transmission/reception charge ofthe services on behalf of users.

For example, in the case where a shopping mall service provider makes anagreement with a communication network provider to thereby launch asponsored data service for on-line shopping, the user may be providedwith an on-line shopping service without payment for a communicationdata charge. In this case, the shopping service provider may expect anincrease in sales due to an increase in the number of users, oradvertisement income through the on-line shopping mall.

An operation of the present disclosure is described hereinafter bytaking an example of cellular network, which, however, should beunderstood as explanation only, not to limit the present disclosure tothe cellular network. It should be understood that various embodimentsof the present disclosure may be applied to a network for catastrophe, aweb real time communication (RTC), and so on as well as the cellularnetwork.

FIG. 13 illustrates a network structure for providing a sponsored dataservice.

Referring to FIG. 13, a WebRTC IMS client (WIC) 1315 is client softwarefor a specific communication service in a UE 1310. According to variousembodiments of the present disclosure, the WIC 1315 may be a client fortaking a web real-time communication (WebRTC) service of 3GPP.

A WebRT web server function (WWSF) 1320 is a web server introduced bythe service provider for providing a service. In some of the variousembodiments of the present disclosure, the WWSF 1320 may be a sever forproviding the WebRTC service. The WWSF 1320 may include a communicationunit for communication with another network node and a controller forcontrolling overall operations of the WWSF. The controller of the WWSFmay control to perform the operation of the WWSF (a web server) thatwill be described with reference to FIGS. 14, 15, 16, 17, 18, 19, and20.

An enhanced P-CSCF (eP-CSCF) 1330 is an improved proxy-call sessioncontrol function (P-CSCF) for supporting an interworking service withthe third party service provider. In some of the various embodiments ofthe present disclosure, the eP-CSCF 1330 may be an improved device forproviding the WebRTC service. In general, the entity that performsadditional operations for providing services is called a serviceenabling server (SES).

The SES 1330 may include a communication unit for communication withanother network node, and a controller for controlling overalloperations of the SES. The controller of the SES may control to performthe operation of the SES that will be described with reference to FIGS.14 to 20.

A PCRF 1340 is an entity for generally controlling the QoS or chargingfor services of the providers, according to the present disclosure. ThePCRF may include a communication unit for communication with anothernetwork node, and a controller for controlling overall operations of thePCRF. The controller of the PCRF may control to perform the operation ofthe PCRF that will be described with reference to FIGS. 14 to 20.

A P-GW 1350 (i.e., a policy and charging enforcement function (PCEF))may apply and execute a rule, i.e., a policy and charging control rule,that is to be applied by the PCRF 1340. The P-GW may include acommunication unit for communication with another network node, and acontroller for controlling overall operations of the P-GW. Thecontroller of the P-GW may control to perform the operation of the P-GWthat will be described with reference to FIGS. 14 to 20.

Although the network structure for providing the 3GPP WebRTC service isadopted for the simplicity and clarification of explanation in thedescription of the drawings and the following various embodiments of thepresent disclosure, the primary subject matter of the present disclosureis not limited to the WebRTC service, and it may be applied to other webservices without significant modification. In this case, the WIC 1315inside the UE 1310 may be comprised of client software for general webservices. In addition, the WWSF 1320, and the eP-CSCF 1330 may becomprised of a general web server, and a network device for supportinginterwork between the network provider and the third party serviceprovider, respectively.

In addition, the UE 1310 may refer to the WIC 1315 in the UE in thefollowing various embodiments of the present disclosure.

FIG. 14 illustrates a method for providing a sponsored data service to auser according to an embodiment of the present disclosure.

Referring to FIG. 14, A UE 1410 may transmit a request message to a webserver (the WWSF) 1420 in order to take a web service provided atoperation S1401. The message may be a message using hypertext transferprotocol (HTTP GET or POST methods, and may include a user ID, and auniform resource identifier (URI) for requested pages or resources. Themessage may further includes a PLMN ID for the terminal.

The UE 1410 and the web server 1420 may additionally exchange messageswith each other. During the operation of exchanging messages,information on mutual authentication between the UE and the web servermay be exchanged at operation S1403.

The web server 1420 may transfer information for providing the webservice of sponsored data to the UE 1410 at operation S1405. The messagemay be a message using HTTP GET, POST or PUT methods, and may include anaccess token that shows that access of the UE to the communicationprovider network and use of the sponsored data service have beenapproved. In addition, the message may further include a sponsor ID, andan application service provider identifier (ASP ID). Furthermore, themessage may include a PLMN ID. Although the access token is separatedfrom other service-related information in the description above, allkinds of service-related information may be included in the accesstoken.

The access token is information that is configured in a format agreed bythe service provider and the communication network provider, and theaccess token may be preliminarily issued by the communication networkprovider to be thereby transferred to the service provider.Particularly, the access token may contain information stating that theUE has been approved to use the sponsored data service, and mayadditionally include information showing the properties (e.g., maximumdata usage, allowed time, the type of service, and the like) ofsponsored data.

The access token is information to determine authority for a specificservice or a resource, which is encoded according to a predeterminedrule between the web server and the communication provider network (theSES in the present disclosure). In addition, in order to prevent abuseor spoofing thereof, the access token should be used under securityaccording to a predetermined rule between the same. To this end, thefollowing method may be used.

The network provider provides a group of access tokens that may beissued to users in the web server, and the web server uses the accesstokens one by one.

The network provider and the web server have credible authenticationinformation (e.g., pre-shared key), and create and verify the accesstoken according to the same rule. For example, the web server createsthe access token using at least one of a user ID, a service provider ID(the sponsor ID, or application service provider ID), current time, aPLMN ID, or other service-related information, and a pre-shared key. Thecommunication provider network (SES) verifies whether or not a receivedaccess token is valid using the information above and the pre-sharedkey.

The UE 1410 may transmit a service request message for using a servicethrough the communication provider network to a SES 1430 (or theeP-CSCF) at operation S1407. The SES 1430 may be an operator server (ora network operator server) and the operator server may be correspondingto the PLMN ID of the terminal. The message may be encoded using theHTTP protocol, or the SIP protocol. Particularly, in using the SIPprotocol, the message may use a register method or an invite method. Therequest message may include the access token received in the operationabove. In addition, the request message may further include the sponsorID and the ASP ID. In addition, the request message may further includethe PLMN ID of the communication network provider. In addition, therequest message may further include additional information (e.g., ID, oraddress) of the web service to be provided to the user.

The SES 1430 (or network operator server) stores information related tothe access token. The access token is information that is configured ina format agreed by the service provider and the communication networkoperator server, and the access token may be preliminarily issued by thecommunication network operator server to be thereby transferred to theservice provider. The access token may correspond to a PLMN ID of thenetwork operator server. The SES 1430 may check whether the UE isentitled to use the sponsored data service through the informationreceive from the UE at operation S1409. The SES 1430 may check whetherthe UE is entitled to use the sponsored data service based on theinformation received from the UE and the information related to theaccess token. During the operation, the SES 1430 may use a part of orall of the access token transmitted from the UE 1410. In addition, theSES 1430 may perform information exchange with the UE 1410 foradditional authentication and security.

The network operator server may include a transmitting/receiving unit, amemory, and a controller. In addition the controller is configured tostore first information related to a token authorized by the networkoperator and a service provider, wherein the token corresponds to a PLMNID of the network operator, receive second information requesting thesponsored service from a terminal, determine whether the terminal isauthorized to use the sponsored service based on the first informationrelated to the token and the second information requesting the sponsoredservice and transmit third information indicating whether the terminalis authorized to use the sponsored service. The sponsored service is aspecific service that the service provider pays charge of a trafficbetween the terminal and the service provider to the network operator.

If the UE 1410 is entitled to use the sponsored data service, the SES1430 may transmit a policy configuration request message to a PCRF 1440to begin the sponsored data service at operation S1411. The message mayuse a diameter protocol. The message may use one of the instructions,such as “AA request,” “Accounting request,” “Credit-Control request,” or“Re-Auth request.” The message may include the sponsor ID and the ASPID. In addition, the message may further include the PLMN ID of thecommunication network provider.

In addition, the message may include a service descriptor by which aservice data flow of an actual service may be recognized. The servicedescriptor may include at least one of an IP address, a port, a domainname, an application ID, or a URI, by which the service is to beprovided. In addition, the message may include information showing theproperties (e.g., data usage, allowed time, charging method, and thelike) of the sponsored data service, and the information may be obtainedthrough a part of or all of the access token received from the UE.Hereinafter, a service descriptor and a service flow descriptor areregarded as the same meaning.

The PCRF 1440 may create a PCC rule, based on the information receivedfrom the SES 1430, or may renew an old PCC rule that has been previouslycreated for use at operation S1413. Particularly, the created or renewedPCC rule may include information on the sponsored data.

The PCRF 1440 may transmit a message for transferring the created orrenewed PCC rule to a P-GW 1450 (PCEF) at operation S1415. The messagemay use a diameter protocol. The message may use one of theinstructions, such as “AA request,” “Accounting request,”“Credit-Control request,” or “Re-Auth request.” The message may includea charging key for separate charging of the sponsored data. The chargingkey for the sponsored data service may not be allotted to each user, butthe charging key may be allotted to be shared with respect to a specificsponsor and a specific application service provider. In addition, themessage may include a service descriptor by which a service data flow(SDF) to be charged according to the sponsored charging method may beidentified. If the UE is not entitled to use data services except forthe sponsored data service, the service descriptor may be configured sothat a gate is closed in the case of the SDF except for the SDF to whichthe sponsored charging is applied.

The P-GW 1450 (PCEF) may begin to control charging and traffic accordingto the received PCC rule at operation S1417. Particularly, the sponsoreddata is charged for, by using not a general charging method but thereceived charging key. In the case where use of specific data is notallowed (e.g., when all of data services except for the sponsored dataservice are blocked), the PCEF 1450 may control traffic according to thegate status of the received PCC rule.

The P-GW 1450 may transmit a response message informing that therequested PCC rule has been successfully applied, to the PCRF 1440 atoperation S1419. The message may use one of the instructions, such as“AA request,” “Accounting request,” “Credit-Control request,” or“Re-Auth request.”

The PCRF 1440 may transmit a response message informing that the rulefor the request sponsored data service has been successfully applied, tothe SES 1430 at operation S1421. This message may use a diameterprotocol. The message may use one of the instructions, such as “AArequest,” “Accounting request,” “Credit-Control request,” or “Re-Authrequest.”

The SES 1430 may transmit a message informing that registration of aservice is completed, to the UE 1410 at operation S1423. This messagemay be encoded using the HTTP protocol, or the SIP protocol.Particularly, in the case of using the SIP protocol, the message may bea message using 200 OK. The message may include information stating thatthe sponsored data service has been applied. In addition, the messagemay include information (e.g., maximum allowed data usage, allowed time,and the like) of the sponsored data service. The message may includeauthentication result which indicates whether the UE 1410 has anauthority to use, perform or apply the sponsored data service.

When the creation or correction of an EPS bearer is required due to thesponsored data service, the P-GW 1450 may trigger an operation for thesame at operation S1425. In this operation, packet filters created bythe P-GW 1450 for the sponsored data service may be installed in the UE.In the case where use of specific data is not allowed (e.g., when all ofdata services except for the sponsored data service are blocked), the UE1410 may be installed with packet filters that are configured to allowpacket transmission/reception for a specific IP flow as well.

The UE 1410 may use the web service in the sponsored data method. Wheninformation on the sponsored data service is received through theoperation above, the information may be displayed to the user atoperation S1427. The UE 1410 may output or display additionalinformation according to the methods described FIGS. 21 to 26.

The access token may include more detailed information for the sponsoreddata service in the various embodiments of the present disclosure. Forexample, the access token may include information on user grades. Thatis, the provided sponsored data service may be differentiated dependingon the UE grades (or priority). To this end, the service provider mayissue the access token to be different according to the service gradesof users, and the UE 1410 that has received the access token may forwardthe same to the SES 1430. Then, the SES 1430 may separate user gradesaccording to the access token. According to this, the properties (e.g.,maximum allowed data usage, allowed time, charging method, and the like)of the sponsored data service may be differentiated. More specifically,for example, the sponsored data service may be given up to 1 GB to theUE 1410 of more than a predetermined grade, whereas it may be given upto 200 MB to the UE 1410 of less than the predetermined grade.

FIG. 15 illustrates a modification of FIG. 14, in which a charging keyis not used.

Referring to FIG. 15, operations S1501 to S1513 are identical or similarto operations S1401 to S1413 of FIG. 14, so the detailed descriptionthereof will be omitted.

In operation S1515, a PCRF 1540 may transmit a message for transferringthe created or renewed PCC rule to a P-GW 1550 (PCEF). The message mayuse a diameter protocol. The message may use one of the instructions,such as “AA request,” “Accounting request,” “Credit-Control request,” or“Re-Auth request.” The request message may further include the sponsorID and the ASP ID. In addition, the message may include a servicedescriptor for identifying an SDF to be charged for the sponsored dataservice. If the UE is not entitled to use data services except for thesponsored data service, the service descriptor may be configured so thata gate is closed in the case of the SDF except for the SDF of thesponsored data service.

The P-GW 1550 (PCEF) may begin to control charging and traffic accordingto the received PCC rule at operation S1517. Particularly, the sponsoreddata is charged for, by not using a general charging method but usingthe received sponsor ID and the ASP ID with respect to the sponsor and aspecific service provider. In the case where use of specific data is notallowed (e.g., when all of data services except for the sponsored dataservice are blocked), the PCEF 1550 may control traffic according to thegate status of the received PCC rule.

Next operations are identical or similar to the operations of FIG. 14,so the detailed description thereof will be omitted.

In the various embodiments of FIG. 14 and FIG. 15, the UE 1410 or 1510may receive information from the web server 1420 or 1520, and the PCCrule may be created for the sponsored data service corresponding to theweb service. Particularly, the SES 1430 or 1530, or the PCRF 1440 or1540 should identify the IP flow (or the service data flow) of thesponsored data service. If the web server has a constant address orport, it may be pre-configured in the SES 1430 or 1530, or the PCRF 1440or 1540 of the communication provider network for use. However, if theaddress or port of the web server is dynamically changed in the case ofa contents delivery network (CDN), cache, or NAT, it is impossible topre-configure the same. Thus, operations S1519 to S1527 are similar tooperations S1419 to S1427 of FIG. 14 and therefore a detaileddescription thereof will be omitted.

In order to address the problem above, the embodiment of the presentdisclosure provides a method by which a server of the service providermay transfer addresses (addresses and ports), which are to be used forthe service, to the UE 1510, and the UE may forward the same to thecommunication provider network. Accordingly, the embodiment of thepresent disclosure provides a method in which, even with dynamicaddresses of the web service (and the content therein), the IP flow ofthe sponsored data service may be accurately identified. Hereinafter,the address refers to information on the location where a specifictraffic occurs, including a URI as well as an IP address, a port, or adomain name.

FIG. 16 illustrates a method for additionally transferring an address ofa web service according to an embodiment of the present disclosure.

Referring to FIG. 16, operations S1601 to S1603 are identical or similarto operations S1401 to S1403 of FIG. 14, so the detailed descriptionthereof will be omitted.

In operation S1605, a web server 1620 may transfer information forproviding the web service as sponsored data to a UE 1610 at operationS1605. The message may be a message using HTTP GET, POST or PUT methods,and may include an access token that shows that access of the UE to thecommunication provider network and use of the sponsored data service hasbeen approved. In addition, the message may further include the sponsorID, and the ASP ID. Furthermore, the message may include the PLMN ID ofthe communication network provider. Although the access token isseparated from other service-related information in the descriptionabove, all kinds of service-related information may be included in theaccess token.

The access token is information that is configured in a format agreed bythe service provider and the communication network provider, and theaccess token may be preliminarily issued by the communication networkprovider to be thereby transferred to the service provider.Particularly, the access token may contain information stating that theUE has been approved to use the sponsored data service, and mayadditionally include information showing the properties (e.g., maximumdata usage, allowed time, the type of service, and the like) ofsponsored data. Particularly, the message may include an address (or anaddress list) to be accessed by the UE for the service. For example, inthe case where the user should download image data from a URI 1 andvideo data from a URI 2, respectively, the message may include all ofthe addresses. Such address information is referred to as a service flowdescriptor. The service flow descriptor may be transmitted separatelyfrom, or together with, the access token.

The access token is information to determine authority for a specificservice or a resource, which is encoded according to a predeterminedrule between the web server and the communication provider network (theSES in the present disclosure). In addition, in order to prevent abuseor spoofing, the access token should be used under security according toa predetermined rule between the same. To this end, the following methodmay be used.

The network provider provides a group of access tokens that may beissued to users in the web server, and the web server uses the accesstokens one by one.

The network provider and the web server have credible authenticationinformation (e.g., pre-shared key), and create and verify the accesstoken according to the same rule. For example, the web server createsthe access token using at least one of a user ID, a service provider ID(the sponsor ID, or application service provider ID), current time, aPLMN ID, or other service-related information, and a pre-shared key. Thecommunication provider network (SES) verifies whether or not a receivedaccess token is valid using the information above and the pre-sharedkey.

In operation S1607, the UE 1610 may transmit a service request messagefor using a service through the communication provider network to an SES1630 (or the eP-CSCF). The message may be encoded using the HTTPprotocol, or the SIP protocol. Particularly, in using the SIP protocol,the message may use a register method or an invite method. The requestmessage may include the access token received in the operation above. Inaddition, the request message may further include the sponsor ID and theASP ID. In addition, the request message may further include additionalinformation (e.g., ID, or address) of the web service to be provided tothe user. Particularly, the message may include an address (or anaddress list) to be accessed by the UE for the service. For example, inthe case where the user should download images from a URI 1 and videosfrom a URI 2, respectively, the message may include all of theaddresses. Furthermore, the message may include a PLMN ID of thecommunication network provider. Although the access token is separatedfrom other service-related information including the service address inthe description above, sponsor and service-related information may beincluded in the access token to be encoded.

In operation S1609, the SES 1630 may check whether the UE 1610 isentitled to use the sponsored data service through the informationreceive from the UE 1610. During the operation, the SES 1630 may use apart of or all of the access token transmitted from the UE 1610. Inaddition, the SES 1630 may perform information exchange with the UE 1610for additional authentication and security. In addition, the SES 1630may recognize information to configure the PCC rule or the packetfilters to be installed in the UE, based on a service flow descriptor,i.e., the list of addresses to be accessed by the UE for the servicelater, which is received from the UE 1610.

In operation S1611, if the UE 1610 is entitled to use the sponsored dataservice, the SES 1630 may transmit a policy configuration requestmessage to a PCRF 1640 to begin the sponsored data service. The messagemay use a diameter protocol. The message may use one of theinstructions, such as “AA request,” “Accounting request,”“Credit-Control request,” or “Re-Auth request.” The message may includethe sponsor ID and the ASP ID. In addition, the message may include aservice descriptor by which a service data flow of an actual service maybe recognized.

The service descriptor may include at least one of an IP address, aport, a domain name, an application ID, or a URI, by which the serviceis to be provided. In addition, the message may include informationshowing the properties (e.g., data usage, allowed time, charging method,and the like) of the sponsored data service, and the information may beobtained through a part of or all of the access token received from theUE 1610. The message may include the service flow descriptor, i.e., thelist of addresses to be accessed by the UE 1610 for the service later,which is received from the UE 1610. The information may be used inconfiguring a corresponding SDF, when the PCRF 1640 creates or renewsthe PCC rule for the sponsored data service. The service flow descriptormay be transmitted separately from or together with the access token.

Next operations are identical or similar to operations after theoperation S1413 of FIG. 14, so the detailed description thereof will beomitted.

Although, the charging key is used for the sponsored charging in theembodiment of FIG. 16, as in FIG. 14, the present disclosure is notlimited thereto, and the embodiment may be applied to the servicecharging using the sponsor ID and the ASP ID, as in FIG. 15. In thiscase, operations S1613 to S1617 of FIG. 16 may be replaced withoperations S1513 to S1517 of FIG. 15. Operations S1619 to S1627 aresimilar to operations S1419 to S1427 of FIG. 14 and therefore a detaileddescription thereof will be omitted.

According to an extended embodiment of the present disclosure, aconditional sponsored data service may be provided. That is, thesponsored data service may be provided only when a specific condition issatisfied. More specifically, when the user uses an on-line shoppingservice, the charging in the sponsored data method may be withheld.Then, once the user actually buys a product, the service provider maypay for the data on behalf of the user. The condition above may beconfigured in the server for providing the sponsored data service.

FIG. 17 illustrates a method for providing a conditional free sponsoreddata service according to an embodiment of the present disclosure.

Referring to FIG. 17, a UE 1710, a web server 1720, and thecommunication provider network have completed information exchange forusing the sponsored data service according to the various embodiments ofFIGS. 14 to 17. The present embodiment is different from the variousembodiments above in that the web service provider does not pay for allof the data charges resulting from the sponsored data service, but paysfor the same provided that a specific condition is satisfied.Accordingly, the UE 1710 may display information on the conditionalsponsored data service through a screen to the user in operation S1701.

The UE 1710 and the service provider web server 1720 exchange messagesfor the service at operation S1703. During the operation above, the webserver 1720 may continue to check whether or not a condition for a freesponsored data service is satisfied at operation S1705. The conditionmay include the case in which transaction of buying a product in theon-line shopping mall has been completed, or the case in whichtransaction of viewing a specific advertisement more than apredetermined number of times has been completed.

If the condition for free data is satisfied, the web server 1720 maytransmit information by which the sponsored data is provided free ofcharge, to the UE 1710 at operation S1707. This message may be a messageusing HTTP GET, POST or PUT methods, and may include an access tokenthat shows that a free sponsored data service has been approved. Inaddition, the message may further include the sponsor ID, and the ASPID.

The access token of the present embodiment is different from the firstaccess token showing that use of the sponsored data has been approved.The access token is information that is configured in a format agreed bythe service provider and the communication network provider, and it maybe preliminarily issued by the communication network provider to bethereby transferred to the service provider. Particularly, the accesstoken of the present embodiment may contain information stating that theUE has been approved to use the sponsored data service, and mayadditionally include information showing that the sponsored data serviceis to be converted into a free service during the service.

The UE 1710 may transmit a service request message for using a servicethrough the communication provider network to an SES 1730 (or theeP-CSCF) at operation S1709. The message may be encoded using the HTTPprotocol, or the SIP protocol. Particularly, in using the SIP protocol,the message may use a register method, an invite method, or an optionmethod. The request message may include the access token received in theoperation above. In addition, the request message may further includethe sponsor ID and the ASP ID.

The SES 1730 may check whether or not the UE 1710 is entitled to use thesponsored data service free of charge through the information receivefrom the UE 1710 at operation S1711. During the operation, the SES 1730may use a part of or all of the access token transmitted from the UE1710. In addition, the SES 1730 may perform information exchange withthe UE 1710 for additional authentication and security.

If the UE 1710 is entitled to use the sponsored data service free ofcharge, the SES 1730 may transmit a request message informing that thesponsored data service is to be converted into a free service, to thePCRF 1740. The message may use a diameter protocol. The message may useone of the instructions, such as “AA request,” “Accounting request,”“Credit-Control request,” “Session Termination request” or “Re-Authrequest.” The message may include the sponsor ID and the ASP ID.

In addition, the message may include a service descriptor by which aservice data flow of an actual service may be recognized. The servicedescriptor may include at least one of an IP address, a port, a domainname, an application ID, or a URI, by which the service is to beprovided. In addition, the message may include information showing theproperties (e.g., data usage, allowed time, charging method, and thelike) of the sponsored data service, and the information may be obtainedthrough a part of or all of the access token received from the UE 1710.Furthermore, the message may include information stating that thesponsored data service is free of charge.

A PCRF 1740 may create a PCC rule, based on the information receivedfrom the SES 1730, or may renew an old PCC rule that has been previouslycreated for use at operation S1715. Particularly, the created or renewedPCC rule may include information stating that the sponsored data serviceis free of charge.

The PCRF 1740 may transmit a message for transferring the created orrenewed PCC rule to a P-GW 1750 (PCEF) at operation S1717. The messagemay use a diameter protocol. The message may use one of theinstructions, such as “AA request,” “Accounting request,”“Credit-Control request,” “Session Termination request,” or “Re-Authrequest.” The message may include a charging key for separate chargingof the sponsored data. The charging key for the sponsored data servicemay not be allotted to each user, but it may be allotted to be sharedwith respect to a specific sponsor and a specific application serviceprovider. In addition, the message may include a service descriptor bywhich an SDF to be charged according to the sponsored charging methodmay be identified.

If the UE 1710 is not entitled to use data services except for thesponsored data service, the service descriptor may be configured so thata gate is closed in the case of the SDF except for the SDF to which thesponsored charging is applied. Furthermore, the message may includeinformation stating that the sponsored data service is free of charge.

The P-GW 1750 (PCEF) may begin to control charging and traffic accordingto the received PCC rule at operation S1719. Particularly, the sponsoreddata is charged for, by not using a general charging method but usingthe received charging key. In the case where use of specific data is notallowed (e.g., when all of data services except for the sponsored dataservice are blocked), the PCEF 1750 may control traffic according to thegate status of the received PCC rule.

In addition, the P-GW 1750 may determine that the sponsored data serviceis free of charge, based on the message received from the PCRF 1740, andthen may not charge for the data, or may invalidate previously collectedcharging information. If necessary, the PCEF 1750 may exchangeinformation with an on-line charging system (OCS) or an off-linecharging system (OFCS) to inform them of the free sponsored dataservice.

The P-GW 1750 may transmit a response message informing that therequested PCC rule has been successfully applied, to the PCRF 1740 atoperation S1721. This message may use a diameter protocol. The messagemay use one of the instructions, such as “AA request,” “Accountingrequest,” “Credit-Control request,” or “Re-Auth request.” The messagemay include information stating that the sponsored data service is freeof charge.

The PCRF 1740 may transmit a response message informing that therequested rule for the sponsored data service has been successfullyapplied, to the SES 1740 at operation S1723. This message may use adiameter protocol. The message may use one of the instructions, such as“AA request,” “Accounting request,” “Credit-Control request,” or“Re-Auth request.” The message may include information stating that thesponsored data service is free of charge.

The SES 1730 may transmit a message informing that messages are to befree of charge, to the UE 1710 at operation S1725. This message may beencoded using the HTTP protocol, or the SIP protocol. Particularly, inthe case of using the SIP protocol, the message may be a message using200 OK.

The UE 1710 may use the web service in a free sponsored data method atoperation S1727. In addition, the UE 1710 display information showingthat a free sponsored data service is to be provided through a screen tothe user.

According to an extended embodiment of FIG. 17, the properties (e.g.,maximum data usage, allowed time, and the like) of sponsored data may bechanged depending on activities of the user as well as the conditionalsponsored data service. For example, in the case where the initialallowed data usage of the sponsored data service is given a traffic of 1GB, if the user satisfies a specific condition (e.g., the case of buyinga product, or viewing advertisement more than a predetermined number oftimes), another 1 GB may be added to the data usage. The condition abovemay be configured in the server for providing the sponsored dataservice.

FIG. 18 illustrates a method for changing a sponsored data serviceaccording to activities of a user.

Referring to FIG. 18, a UE 1810, a web server 1820, and thecommunication provider network have completed information exchange forusing the sponsored data service according to the various embodiments ofFIGS. 14 to 17.

The UE 1810 and the service provider web server 1820 exchange messagesfor the service at operation S1801. For example, web pages for buying aproduct or including advertisement are continuously requested. Duringthe operation above, the web server 1820 may continue to check whetheror not a condition for changing the properties (maximum allowed datausage, or allowed time) of the sponsored data service is satisfied atoperation S1803 is satisfied. The condition may include the case inwhich transaction of buying a product in an on-line shopping mall hasbeen completed, or the case in which transaction of viewing a specificadvertisement more than a predetermined number of times has beencompleted.

If the condition for changing the properties is satisfied, the webserver 1820 may transmit information by which the sponsored data isupgraded, to the UE 1810 at operation S1805. This message may be amessage using HTTP GET, POST or PUT methods, and may include informationfor upgrading the sponsored data service and an access token. Inaddition, the message may further include the sponsor ID, and the ASPID.

The access token of the present embodiment is different from the firstaccess token showing that use of the sponsored data service has beenapproved. The access token is information that is configured in a formatagreed by the service provider and the communication network provider,and the access token may be preliminarily issued by the communicationnetwork provider to be thereby transferred to the service provider.Particularly, the access token may contain information stating that thesponsored data service has been approved to be upgraded. That is, theaccess token may include upgraded information (e.g., upgraded data usageand allowed time) of the sponsored data service. Alternatively, theaccess token may include only information stating that the upgrading ofthe sponsored data service has been approved, and the upgradedinformation (e.g., upgraded data usage, allowed time, charging method,and the like) may be separately transmitted.

The UE 1810 may transmit a service request message for using a servicethrough the communication provider network to the SES 1830 (or theeP-CSCF). The message may be encoded using the HTTP protocol, or the SIPprotocol. Particularly, in using the SIP protocol, the message may use aregister method, an invite method, or an option method. The requestmessage may include the access token received in the operation above. Inaddition, the request message may further include the sponsor ID and theASP ID. The access token may include upgraded information (e.g.,upgraded data usage and allowed time) of the sponsored data service.Alternatively, the access token may include only information statingthat the upgrading of the sponsored data service has been approved, andthe upgraded information (e.g., upgraded data usage, allowed time,charging method, and the like) may be separately transmitted.

The SES 1830 may check whether or not the UE is entitled to use anupgraded sponsored data service through the information receive from theUE 1810 at operation S1809. During the operation, the SES 1830 may use apart of or all of the access token transmitted from the UE 1810. Inaddition, the SES 1830 may perform information exchange with the UE foradditional authentication and security.

If the UE 1810 is entitled to use an upgraded sponsored data service,the SES 1830 may transmit a request message informing that the sponsoreddata service is to be upgraded, to a PCRF 1840 at operation S1811. Themessage may use a diameter protocol. The message may use one of theinstructions, such as “AA request,” “Accounting request,”“Credit-Control request,” “Session Termination request” or “Re-Authrequest.” The message may include the sponsor ID and the ASP ID.

In addition, the message may include a service descriptor by which aservice data flow of an actual service may be recognized. The servicedescriptor may include at least one of an IP address, a port, a domainname, an application ID, or a URI, by which the service is to beprovided. In addition, the message may include information showing theproperties (e.g., data usage, allowed time, charging method, and thelike) of the renewed sponsored data service, and the information may beobtained through a part of or all of the access token received from theUE.

The PCRF 1840 may create a PCC rule, based on the information receivedfrom the SES 1830, or may renew an old PCC rule that has been previouslycreated for use at operation S1813. Particularly, the created or renewedPCC rule may include information showing the properties of the upgradedsponsored data service.

The PCRF 1840 may transmit a message for transferring the created orrenewed PCC rule to a P-GW 1850 (PCEF) at operation S1815. The messagemay use a diameter protocol. The message may use one of theinstructions, such as “AA request,” “Accounting request,”“Credit-Control request,” “Session Termination request,” or “Re-Authrequest.” The message may include a charging key for separate chargingof the sponsored data. The charging key for the sponsored data servicemay not be allotted to each user, but it may be allotted to be sharedwith respect to a specific sponsor and an ASP. In addition, the messagemay include a service descriptor by which an SDF to be charged accordingto the sponsored charging method may be identified. If the UE is notentitled to use data services except for the sponsored data service, theservice descriptor may be configured so that a gate is closed in thecase of the SDF except for the SDF to which the sponsored charging isapplied. Furthermore, the message may include information showing theproperties (e.g., maximum data usage, allowed time, and the like) of theupgraded sponsored data service.

The P-GW 1850 (PCEF) may begin to control charging and traffic accordingto the received PCC rule at operation S1817. Particularly, the sponsoreddata is charged for, by not using a general charging method but usingthe received charging key. In the case where use of specific data is notallowed (e.g., when all of data services except for the sponsored dataservice are blocked), the PCEF 1850 may control traffic according to thegate status of the received PCC rule.

The P-GW 1850 may transmit a response message informing that therequested PCC rule has been successfully applied, to the PCRF 1840 atoperation S1819. This message may use a diameter protocol. The messagemay use one of the instructions, such as “AA request,” “Accountingrequest,” “Credit-Control request,” or “Re-Auth request.”

The PCRF 1840 transmits a response message, which informs that policyapplication for the requested sponsored data service has succeeded, tothe SES 1830 at operation S1821. This message may use a diameterprotocol. The message may use one of the instructions, such as “AArequest,” “Accounting request,” “Credit-Control request,” or “Re-Authrequest.”

Regardless of sequence of the operation, the PCRF 1840 may exchangemessages with a subscription profile repository (SPR) to thereby storeupgraded information of the sponsored data service for the UE 1810 atoperation S1823. This enables the UE 1810 to be continuously providedwith the sponsored data service, even though the UE 1810 has beendetached or deregistered from the communication provider network. In theoperation above, the message using a diameter protocol, for example, aprofile update request message and a profile request answer message, maybe used. The message may include upgraded information of the sponsoreddata service, i.e., maximum allowed data usage, allowed use time, useddata usage, used time, and the like.

The SES 1830 may transmit a message informing that the upgradedsponsored data service is to be applied, to the UE 1810 at operationS1825. This message may be encoded using the HTTP protocol, or the SIPprotocol. Particularly, in the case of using the SIP protocol, it may bea message using 200 OK.

The UE 1810 may use the web service in a sponsored data method accordingto the renewed condition. In addition, the UE 1710 display informationshowing that the properties (e.g., maximum data usage, or allowed time)of the sponsored data service have been changed through a screen to theuser.

The various embodiments of the present disclosure above provide a methodby which the UE informs the SES of the communication provider network ofconnection information for the sponsored data service, and then corenetwork nodes (i.e., the PCRF, and the PCEF) transfer information forproviding the sponsored data service to the UE. According to littlemodification of the present embodiments, the UE may directly transferthe information to the core network nodes without passing through aspecific server.

FIG. 19 illustrates a method for transmitting connection information toa core network node by UE using PCO.

Referring to FIG. 19, a UE 1910 may transmit a request message for usinga web service to a web server 1920 at operation S1901. The message maybe a message using HTTP GET or POST methods, and may include a user ID,and a URI for requested pages or resources. Furthermore, the message mayinclude a PLMN ID of the communication network provider.

The UE 1910 and the web server 1920 may additionally exchange messageswith each other at operation S1903. During the operation above,information on mutual authentication between the UE 1910 and the webserver may be exchanged.

The web server 1920 may transfer information for providing a web serviceof sponsored data, to the UE 1910 at operation S1905. The message may bea message using HTTP GET, POST or PUT methods, and may include an accesstoken showing that access of the UE to the communication providernetwork and use of the sponsored data service have been approved. Inaddition, the message may further include a service flow descriptor, asponsor ID, and an ASP ID. Furthermore, the message may include a PLMNID of the communication network provider. The service flow descriptor isinformation based on IP 5-tuple, or a connection address (the domainname, or the URI). In addition, the access token may include atermination time of the access token, and a session termination time.Although the access token is separated from other service-relatedinformation in the description above, all kinds of service-relatedinformation may be included in the access token. In addition, themessage may include information for identifying validity of the accesstoken or authenticating the same. For example, the message may include amessage authentication code (MAC) for verifying integrity of the accesstoken.

The access token is information that is configured in a format agreed bythe service provider and the communication network provider, and theaccess token may be preliminarily issued by the communication networkprovider to be thereby transferred to the service provider.Particularly, the access token may contain information stating that theUE has been approved to use the sponsored data service, and mayadditionally include information showing the properties (e.g., maximumdata usage, allowed time, the type of service, and the like) ofsponsored data. The access token is information to determine authorityfor a specific service or a resource, which is encoded according to apredetermined rule between the web server and the communication providernetwork (the SES in the present disclosure). In addition, in order toprevent abuse or spoofing, the access token should be used undersecurity according to a predetermined rule between the same. To thisend, the following method may be used.

The network provider provides a group of access tokens that may beissued to users in the web server, and the web server uses the accesstokens one by one.

The network provider and the web server have credible authenticationinformation (e.g., pre-shared key), to thereby verify integrity of theaccess token and authenticate the same. For example, the web servercreates a payload of the access token using at least one of a serviceprovider ID (at least one of the sponsor ID or the application serviceprovider ID), current time, a PLMN ID, a service flow descriptor (e.g.,list of IP 5-tuple, domain name, or URI), a termination time, or otherservice-related information, and creates a message authentication code(MAC) for verifying integrity of the access token, using a pre-sharedkey or a certificate with the payload. The communication providernetwork creates the MAC using the received access token and pre-sharedkey, and verifies validity of the received information by comparing thesame with the received MAC.

Although the MAC is described to be separated from the access token inthe present embodiment, it may be included in the access token. Morespecifically, the access token may include information (e.g. the serviceflow descriptor, the sponsor ID, the ASP ID, and the like) for providingthe sponsored data service, and the MAC created using the informationand the pre-shared key. That is, in this case, the access token is to becreated the remaining part except for the MAC.

The UE 1910 may transmit a request message for a resource to get a dataservice to the communication provider network at operation S1907. Morespecifically, the UE 1910 may transmit a bearer resource allocationrequest message, or a bearer resource modification request message tothe core network node. For example, the core network node may be an MME1930. Hereinafter, the description will be made on the assumption thatthe core network node is the MME. The message may include informationreceived from the web server 1920, which is included in protocolconfiguration option (PCO) to be transmitted. That is, the UE 1910 mayinclude the access token received from the server in the PCO, andtransmit the same. In the case where the access token is separated fromthe MAC, the MAC may be included in the PCO to be transmitted as well.In addition, the UE 1910 may include traffic flow aggregate (TFA) thatis comprised of IP information for the sponsored data service in themessage. The TFA is information created from the service flow descriptorreceived from the server. Even though the UE 1910 has a packet filter(i.e., a match-all filter) that may transmit and receive all of servicedata flows, or has an EPS bearer configured to perform the operationequivalent thereto, the UE 1910 may create and transmit the resourcerequest message in order to use the sponsored data service provided. Ifthe information received from the web server 1920 includes a domain nameor a URI instead of IP address/port information (i.e., IP 5-tuple) ofthe server to be connected by the UE for the service, the UE 1910 mayinclude the address of web servers that have been connected with the UEin the TFA, to be thereby transmitted.

The MME 1930 may begin an operation of creating or correcting the bearercontext together with core network nodes, based the request messagereceived from the UE 1910 at operation S1909. That is, the MME 1930 maycreate a bearer resource command message and may transmit the same tothe SGW. The message may include information included in the messagereceived from the UE 1910, that is, the PCO and the service flowdescriptor. The service flow descriptor may be converted into a form oftraffic aggregate description (TAD) to be thereby included. That is, thepacket filters (information to identify IP 5-tuple) included in theservice flow descriptor may be include in the TAD, and then may beinclude in the message to be thereby transmitted to the SGW. The SGW mayforward the message to a P-GW 1940.

The PGW 1940 may perform an operation of creating or correcting anIP-connectivity access network (CAN) session using the receivedinformation together with a PCRF 1950 at operation S1911. Morespecifically, the P-GW 1940 may transmit a message to the PCRF 1950, andmay perform an operation to receive the PCC rule for the UE 1910. Themessage may use a diameter protocol. The message may use one of theinstructions, such as “AA request,” “Accounting request,”“Credit-Control request,” or “Re-Auth request.” The message may includeinformation on the sponsor ID, i.e., the access token. If the accesstoken is separated from the MAC, the message may include the MAC to betransmitted. In addition, the message may include information (theservice flow descriptor received by TAD, TFT information, or packetfilter information) showing a service flow with respect to the UE. Inaddition, the message may include the PLMN ID of the communicationnetwork provider. The service flow descriptor may include at least oneof the IP 5-tuple (an IP address and port to provide the service), adomain name, an application ID, or a URI.

The PCRF 1950 may create a PCC rule for providing the sponsored dataservice, based on the information received from the P-GW 1940, or mayrenew an old PCC rule at operation S1913. Prior to that, the PCRF 1950may determine whether or not the access token is valid in theinformation received from the P-GW 1940 at operation S1913. Morespecifically, the PCRF 1950 may search for security information fordetermining validity of the access token and the request of the UE 1910with respect to the sponsored data service provider using at least oneof the sponsor ID or the ASP ID, which are included in the receivedinformation, and may determine the validity (or integrity) of thereceived access token and the request of the UE.

More specifically, the PCRF 1950 may search for the stored securityinformation (the pre-shared key or a certificate), using at least one ofthe sponsor ID or the ASP ID, which are included in the access token,and may create a MAC using the security information and the accesstoken. Next, the PCRF 1950 may verify the validity of the receivedaccess token and the sponsored data service request of the UE 1910 bycomparing the same with the received MAC (included in the access token,or received as separate information).

At this time, the PCRF 1950 may exchange information with a separateserver in charge of authentication with respect to the access token(e.g., an authentication authorization accounting (AAA) server). Morespecifically, the PCRF 150 may transmit the received access token to theauthentication server. If the MAC is received separately from the accesstoken, the MAC is transmitted to the authentication server as well. Theauthentication server may determine the validity of the receive accesstoken by performing the operation as described above, and may send theresult back to the PCRF 1950.

When it is determined that the received access token and the request ofthe UE 1910 are valid, the PCRF 1950 may create a PCC rule, or may renewan old PCC rule that has been created before. Particularly, the createdor renewed PCC rule may include information on the sponsored data, andmay use a charging key with respect to a specific sponsor or ASP.

The PCRF 1950 may transmit a message for transferring the created orrenewed PCC rule to the P-GW 1940 (PCEF) at operation S1915. The messagemay use a diameter protocol. The message may use one of theinstructions, such as “AA request,” “Accounting request,”“Credit-Control request,” or “Re-Auth request.” The message may includea charging key for separate charging of the sponsored data. The chargingkey for the sponsored data service may not be allotted to each user, butit may be allotted to be shared with respect to a specific sponsor and aspecific application service provider.

In addition, the message may include information by which an SDF to becharged according to the sponsored charging method may be identified. Ifthe UE is not entitled to use data services except for the sponsoreddata service, the service descriptor may be configured so that a gate isclosed in the case of the SDF except for the SDF to which the sponsoredcharging is applied.

If the service flow descriptor (that is, included in the access token)that has been received by the P-GW 1940 from the UE 1910 through the PCOincludes a domain name or a URI instead of IP address/port information,the P-GW 1940 may inspect a domain name system enquiry requesttransmitted by the UE 1910 or a response message thereto. If a requesteddomain name is included in the domain name or the URI list, which areincluded in the service flow descriptor, the P-GW 1940 may perform anoperation of adding a responded IP address information (the IP addressand, if necessary, an additional port number) to packet filters thatidentify the sponsored traffic (i.e., an SDF template of the PCC rulefor the sponsored data service). To this end, the P-GW 1940 may add thepacket filters without exchanging information with the PCRF 1950, or maytransmit a request for adding the IP address information to the PCC ruleof the sponsored data service, to the PCRF 1950.

The P-GW 1940 (PCEF) may begin to control charging and traffic accordingto the received PCC rule at operation S1917. Particularly, the sponsoreddata is charged for, by using not a general charging method but thereceived charging key. In the case where use of specific data is notallowed (e.g., when all of data services except for the sponsored dataservice are blocked), the PCEF 1950 may control traffic according to thegate status of the received PCC rule.

When the creation or correction of an EPS bearer is required due to thesponsored data service, the P-GW 1940 may trigger an operation for thesame at operation S1919. In this operation, the packet filters createdby the P-GW 1940 for the sponsored data service may be installed in theUE 1910. In the case where use of specific data is not allowed (e.g.,when all of data services except for the sponsored data service areblocked), the UE 1910 may be installed with packet filters that areconfigured to allow packet transmission/reception for a specific IP flowas well.

Afterwards, the UE 1910 may use the web service in the sponsored datamethod at operation S1921. When information on the sponsored dataservice is received through the operation above, it may be displayed tothe user.

The access token may include more detailed information for the sponsoreddata service in the various embodiments of the present disclosure. Forexample, the access token may include information on user grades. Thatis, the sponsored data service may be differentiated depending on the UEgrades (or priority). To this end, the service provider may issue theaccess token to be different according to the service grades of users,and the UE that has received the access token may transfer the same tothe communication provider network. A core network node (P-GW) mayseparate user grades according to the access token. According to this,the properties (e.g., maximum allowed data usage, allowed time, chargingmethod, and the like) of the sponsored data service may bedifferentiated. More specifically, for example, the sponsored dataservice may be given up to 1 GB to the UE of more than a predeterminedgrade, whereas it may be given up to 200 MB to the UE of less than thepredetermined grade.

Although the embodiment of FIG. 19 discloses a method by which the P-GWtransmits the access token received through the PCO to the PCRF, and thePCRF verifies the same for use, in another embodiment of the presentdisclosure, the P-GW processes the received access token by itself, andtransmits necessary information to the PCRF to thereby create or renewthe PCC rule.

FIG. 20 illustrates a method for transmitting connection information toa core network node by UE using the PCO.

Referring to FIG. 20, a UE 2010 may transmit a request message for usinga web service to a web server 2020 at operation S2001. The message maybe a message using HTTP GET or POST methods, and may include a user ID,and a URI for requested pages or resources. Furthermore, the message mayinclude a PLMN ID of a communication network provider who is selected bythe user.

The UE 2010 and the web server 2020 may additionally exchange messageswith each other at operation S2003. During the operation above,information on mutual authentication between the UE 2010 and the webserver may be exchanged.

The web server 2020 may transfer information for providing a web serviceof sponsored data, to the UE 2010 at operation S2005. The message may bea message using HTTP GET, POST or PUT methods, and may include an accesstoken showing that access of the UE to the communication providernetwork and use of the sponsored data service have been approved. Inaddition, the message may further include a service flow descriptor(that is the same as the service descriptor), a sponsor ID, and an ASPID. Furthermore, the message may include a PLMN ID of the communicationnetwork provider. The service flow descriptor is information based on IP5-tuple, or a connection address (the domain name, or the URI). Inaddition, the access token may include a termination time of the accesstoken, and a session termination time. Although the access token isseparated from other service-related information in the descriptionabove, all kinds of service-related information may be included in theaccess token. In addition, the message may include information foridentifying validity of the access token or authenticating the same. Forexample, the message may include a message authentication code (MAC) forverifying integrity of the access token.

The access token is information that is configured in a format agreed bythe service provider and the communication network provider, and it maybe preliminarily issued by the communication network provider to bethereby transferred to the service provider. Particularly, the accesstoken may contain information stating that the UE has been approved touse the sponsored data service, and may additionally include informationshowing the properties (e.g., maximum data usage, allowed time, the typeof service, and the like) of sponsored data. The access token isinformation to determine authority for a specific service or a resource,which is encoded according to a predetermined rule between the webserver and the communication provider network (the SES in the presentdisclosure). In addition, in order to prevent abuse or spoofing, theaccess token should be used under security according to a predeterminedrule between the same. To this end, the following method may be used.

The network provider provides a group of access tokens that may beissued to users in the web server, and the web server uses the accesstokens one by one.

The network provider and the web server have credible authenticationinformation (e.g., pre-shared key), to thereby verify integrity of theaccess token and authenticate the same. For example, the web servercreates a payload of the access token using at least one of a serviceprovider ID (at least one of the sponsor ID or the application serviceprovider ID), current time, a PLMN ID, a service flow descriptor (e.g.,list of IP 5-tuple, domain name, or URI), a termination time, or otherservice-related information, and creates a message authentication code(MAC) for verifying integrity of the access token, using a pre-sharedkey or a certificate with the payload. The communication providernetwork creates the MAC using the received access token and pre-sharedkey, and verifies validity of the received information by comparing thesame with the received MAC.

Although the MAC is described to be separated from the access token inthe present embodiment, the access token may be included in the accesstoken. More specifically, the access token may include information (e.g.the service flow descriptor, the sponsor ID, the ASP ID, and the like)for providing the sponsored data service, and the MAC created using theinformation and the pre-shared key. That is, in this case, the accesstoken is to be created the remaining part except for the MAC.

The UE 2010 may a request message for a resource to get a data serviceto the communication provider network at operation S2007. Morespecifically, the UE 2010 may transmit a bearer resource allocationrequest message, or a bearer resource modification request message tothe core network node. For example, the core network node may be a MME2030. Hereinafter, the description will be made on the assumption thatthe core network node is the MME. The message may include informationreceived from the web server 2020, which is included in protocolconfiguration option (PCO) to be transmitted. That is, the UE mayinclude the access token received from the server in the PCO, and maytransmit the same. In the case where the access token is separated fromthe MAC, the MAC may be included in the PCO to be transmitted as well.In addition, the UE 2010 may include traffic flow aggregate (TFA) thatis comprised of IP information for the sponsored data service in themessage. The TFA is information created from the service flow descriptorreceived from the server. Even though the UE 2010 has a packet filter(i.e., a match-all filter) that may transmit and receive all of servicedata flows, or has an EPS bearer configured to perform the operationequivalent thereto, the UE 2010 may create and transmit the resourcerequest message in order to use the sponsored data service provided. Ifthe information received from the web server 2020 includes a domain nameor a URI instead of IP address/port information (i.e., IP 5-tuple) ofservers to be connected by the UE for the service, the UE 2010 mayinclude the address of a web server that has been connected with the UEin the TFA, to be thereby transmitted.

The MME 2030 may begin an operation of creating or correcting the bearercontext together with core network nodes, based the request messagereceived from the UE 2010 at operation S2009. That is, the MME 2030 maycreate a bearer resource command message and may transmit the same tothe SGW. The message may include information included in the messagereceived from the UE 2010, that is, the PCO and the service flowdescriptor. The service flow descriptor may be converted into a form oftraffic aggregate description (TAD) to be thereby included. That is, thepacket filters (information to identify IP 5-tuple) included in theservice flow descriptor may be included in the TAD, and then may beincluded in the message to be thereby transmitted to the SGW. The SGWmay forward the message to a P-GW 2040.

The P-GW 2040 may perform an operation of creating or correcting anIP-CAN session using the received information together with a PCRF 2050.Prior to that, the P-GW 2040 may determine whether or not the accesstoken in the received information is valid at operation S2011. Morespecifically, the P-GW 2040 may search for security information fordetermining validity of the access token and the request of the UE 2010with respect to the sponsored data service provider using at least oneof the sponsor ID or the ASP ID, which are included in the receivedinformation. The P-GW 2040 may determine the validity (or integrity) ofthe received access token and the request of the UE 2010.

More specifically, the P-GW 2040 may search for the stored securityinformation (the pre-shared key or a certificate), using at least one ofthe sponsor ID or the ASP ID, which are included in the access token,and may create a MAC using the security information and the accesstoken. Next, the P-GW 2040 may verify validity of the received accesstoken and the sponsored data service request of the UE by comparing thesame with the received MAC (included in the access token, or receive asseparate information).

At this time, the P-GW 2040 may exchange information with a separateserver in charge of authentication with respect to the access token(e.g., an authentication authorization accounting (AAA) server). Morespecifically, the P-GW 2040 may transmit the received access token tothe authentication server. If the MAC is received separately from theaccess token, the MAC is transmitted to the authentication server aswell. The authentication server may determine the validity of thereceive access token by performing the operation as described above, andmay send the result back to the P-GW 2040.

If the verification is succeeds, the P-GW 2040 may transmit a message tothe PCRF 2050, to thereby perform an operation of receiving the PCC ruleof the UE 2010 at operation S2013. The message may use a diameterprotocol. The message may use one of the instructions, such as “AArequest,” “Accounting request,” “Credit-Control request,” or “Re-Authrequest.” The request message may further include information on thesponsored data service, i.e., at least one of a sponsor ID and an ASPID. In addition, the message may include information (the service flowdescriptor received by TAD, TFT information, or packet filterinformation) showing a service flow with respect to the UE. In addition,the message may include a PLMN ID of the communication network provider.The service flow descriptor may include at least one of the IP 5-tuple(an IP address and port to provide the service), a domain name, anapplication ID, or a URI.

The PCRF 2050 may create a PCC rule for providing the sponsored dataservice, or may renew an old PCC rule, based on the information receivedfrom the P-GW 2040 at operation S2015. Particularly, the created orrenewed PCC rule may include information on the sponsored data, and tothis end, a charging key for a specific sponsor and a specific ASP isused.

The PCRF 2050 may transmit a message for transferring the created orrenewed PCC rule to the P-GW 2040 (PCEF) at operation S2017. The messagemay use a diameter protocol. The message may use one of theinstructions, such as “AA request,” “Accounting request,”“Credit-Control request,” or “Re-Auth request.” The message may includea charging key for separate charging of the sponsored data. The chargingkey for the sponsored data service may not be allotted to each user, butit may be allotted to be shared with respect to a specific sponsor and aspecific application service provider.

In addition, the message may include a service descriptor by which anSDF to be charged according to the sponsored charging method may beidentified. If the UE is not entitled to use data services except forthe sponsored data service, the service descriptor may be configured sothat a gate is closed in the case of the SDF except for the SDF to whichthe sponsored charging is applied.

If the service flow descriptor (that is, included in the access token)that has been received by the P-GW 2040 from the UE 2010 through the PCOincludes a domain name or a URI instead of IP address/port information,the P-GW 2040 may inspect a domain name system enquiry requesttransmitted by the UE 2010 or a response message thereto. If a requesteddomain name is included in the domain name or the URI list, which areincluded in the service flow descriptor, the P-GW 2040 may perform anoperation of adding a responded IP address information (the IP addressand, if necessary, an additional port number) to packet filters thatidentify the sponsored traffic (i.e., an SDF template of the PCC rulefor the sponsored data service). To this end, the P-GW 2040 may add thepacket filters without exchanging information with the PCRF 2050, or maytransmit a request for adding the IP address information to the PCC ruleof the sponsored data service, to the PCRF 2050.

The P-GW 2040 (PCEF) may begin to control charging and traffic accordingto the received PCC rule at operation S2019. Particularly, the sponsoreddata is charged for, by using not a general charging method but thereceived charging key. In the case where use of specific data is notallowed (e.g., when all of data services except for the sponsored dataservice are blocked), the PCEF 2050 may control traffic according to thegate status of the received PCC rule.

When the creation or correction of an EPS bearer is required due to thesponsored data service, the P-GW 2040 may trigger an operation for thesame at operation S2021. In this operation, the packet filters createdby the P-GW 2040 for the sponsored data service may be installed in theUE 2010. In the case where use of specific data is not allowed (e.g.,when all of data services except for the sponsored data service areblocked), the UE 2010 may be installed with packet filters that areconfigured to allow packet transmission/reception for a specific IP flowas well.

The UE 2010 may use the web service in the sponsored data method atoperation S2023. When information on the sponsored data service isreceived through the operation above, it may be displayed to the user.

The access token may include more detailed information for the sponsoreddata service in the various embodiments of the present disclosure. Forexample, the access token may include information on user grades. Thatis, the provided sponsored data service may be differentiated dependingon the UE grades (or priority). To this end, the service provider mayissue the access token to be different according to the service gradesof users, and the UE that has received the access token may forward thesame to the communication provider network. A core network node (P-GW)may separate user grades according to the access token. According tothis, the properties (e.g., maximum allowed data usage, allowed time,charging method, and the like) of the sponsored data service may bedifferentiated. More specifically, for example, the sponsored dataservice may be given up to 1 GB to the UE of more than a predeterminedgrade, whereas it may be given up to 200 MB to the UE of less than thepredetermined grade.

Although the charging of the sponsored data service is changed accordingto the agreement between the service provider and the communicationnetwork provider, and the activities of the user in the presentspecification and FIGS. 14 to 20, it is only an example for convenienceof explanation and understanding of the invention, and the presentinvention is not limited thereto. In the present invention, thesponsored data and the policy for applying the same may include atraffic control that includes a QoS control, as well as the charging.That is, according to the various embodiments of the present invention,the user may be provided with the sponsored data service, and thesponsored data service may encompass the charging and provision ofspecial QoS. For example, the sponsored data service enables the user touse a specific web service with the guaranteed QoS, compared to otherservices that do not adopt the sponsored data service or users who arenot provided with the sponsored data service.

Although the access token, and the information related to the serviceand the sponsor (e.g., the sponsor ID, the ASP ID, the service flowdescriptor, and the like) are separately transmitted in the presentembodiments, the information related to the service and the sponsor maybe encoded in the access token to be thereby transmitted.

When the user uses the sponsored data service, the sponsored dataservice is required to provide information on the sponsored data serviceto the user. For example, the user wishes to know the volume of datathat is processed as the free sponsored data service among the data thathe or she has transmitted/received. In the case of a conditionalsponsored data service (e.g., the sponsored data service is limited tothe total amount of data or service time), the user is likely to want toknow information on the remaining time for the sponsored data service.Hereinafter, various methods for informing of the amount of dataprocessed as the sponsored data service will be described.

FIG. 21 illustrates a method for calculating a volume of datatransmitted and received through a sponsored data service in a UE andinforming the user of a same according to an embodiment of the presentdisclosure. Packet filters may be installed for the sponsored dataservice in the UE. The packet filters are configured to allow packettransmission/reception for a specific IP flow as well, and the volume ofdata transmitted and received through the sponsored data service in theUE is calculated based on the operation of the packet filters.

Referring to FIG. 21, the UE provided with the sponsored data servicemay receive the access token for the sponsored data service from theserver or the network entity at operation S2110. The access token mayinclude at least one piece of information such as a sponsor ID of thesponsor provider, an ASP ID indicating service applications, an address(IP 5 tuple, or a uniform resource locator (URL) list) of the serverproviding the data service, creation data and time of the access token,a random number value, a key set ID for identifying a key used insecurity, an algorithm ID for identifying an algorithm used in security,and a message authentication code.

The UE may identify whether the data traffic transmitted and received bythe UE corresponds to the sponsored data service, based on theinformation include in the access token. For example, the UE may extractidentification information (e.g., a specific access point name (APN), aspecific IP 5 tuple, a server URL, and the like) for identifying thetraffic corresponding to the sponsored data service, i.e., an IP flow,from the received access token at operation S2120. The UE may store theextracted identification information. The UE may perform an operation ofseparating the traffic corresponding to the sponsored data service (thatis, the traffic not to be charged) among the traffic transmitted andreceived by the UE, based on the extracted information. That is, the UEmay identify the traffic corresponding to the sponsored data service,based on the extracted information.

The UE may transmit a service request message including the receivedaccess token to the provider network at operation S2130. The UE may getthe approval message for the sponsored data service by a response to themessage.

Although the UE extracts identification information for identifying thetraffic corresponding to the sponsored data service form the receivedaccess token, and gets the approval message for the sponsored dataservice from the provider network in the embodiment above, theoperations above may be performed in the opposite order, or may bemodified. Particularly, if the validity of the access token receivedfrom the server cannot be identified, the UE may transmit the accesstoken to the provider network to get the validity of the access token.Then, after approval for the sponsored data service, the UE may extractand store the service information included in the access token for use.

The UE may transmit or receive the user plane data packets to or fromthe provider network at operation S2140.

When the user plane data packets are transmitted or received, the UE maydetermine whether the user plane data packets are included in thetraffic for the sponsored data service that has been stored before atoperation S2150. The UE may determine whether or not the user trafficcorresponds to the sponsored data service using the identificationinformation extracted from the access token. The UE may determinewhether or not the user traffic corresponds to the sponsored dataservice, based on the determination of whether the information includedin the user plane data packet corresponds to the identificationinformation. For example, the UE may identify whether or not the PDNconnection or the EPS bearer context (e.g., APN, QCI/Address ResolutionProtocol (ARP), and the like) included in the user plane data packetsmatches the identification information that has been extracted (orstored) to thereby determine whether the user traffic corresponds to thesponsored data service. In addition, the UE may identify whether some ofor all of the IP address/port or the URL of the user plane data packetsmatch the stored information to thereby determine whether the usertraffic corresponds to the sponsored data service.

If the transmitted and received user plane data packets correspond tothe sponsored data service traffic, the related user plane data packetsmay be managed as the traffic of the sponsored data service at operationS2160. For example, the UE may add the transmitted and received packetsto the amount of sponsored data based on the packet filters. In additionto the method of adding the amount of traffic, the amount of servicetraffic may be managed by the UE in various ways. Although not describedin the present disclosure, the initial value of the amount of sponsoreddata may be initiated or may be configured as a specific value when thesponsored data service is started. In addition, the traffic may bemanaged periodically at a predetermined time, or irregularly wheneverthe user plane data packets are created.

The UE may inform the user of the calculated volume of sponsored data(the amount of sponsored data) as information of the sponsored dataservice at operation S2170. The UE may output information on the amountof sponsored data service traffic. For example, the information on theamount of sponsored data service traffic includes total amount ofsponsored data service traffic during a preconfigured period. Theinformation may be expressed as graphs or numbers (e.g., by a byteunit). The information may be output by various output means, such as avoice, a vibration, sensors, and the like, as well as displaying theinformation on a screen of the UE.

FIG. 22 illustrates the operation of the UE in the conditional sponsoreddata service according to an embodiment of the present disclosure.

Referring to FIG. 22, the UE provided with the sponsored data servicemay receive the access token for the sponsored data service from theserver or the network entity at operation S2210.

The UE may identify whether the data traffic transmitted and received bythe UE corresponds to the sponsored data service, based on theinformation included in the access token. For example, the UE mayextract identification information (e.g., a specific APN, a specific IP5 tuple, a server URL, and the like) for identifying the trafficcorresponding to the sponsored data service, i.e., an IP flow, from thereceived access token at operation S2220. The UE may store the extractedidentification information. The UE may perform an operation ofseparating the traffic corresponding to the sponsored data service (thatis, the traffic not to be charged) among the traffic transmitted andreceived by the UE, based on the extracted information. That is, the UEmay identify the traffic corresponding to the sponsored data service,based on the extracted information. In addition, the UE may extractservice restriction information (the maximum amount of data to which thesponsored data service is provided free of charge) from the accesstoken. In addition, the UE may store the extracted service restrictioninformation.

The UE may transmit a service request message including the receivedaccess token to the provider network at operation S2230. The UE may getthe approval message for the sponsored data service by a response to themessage.

Although the UE extracts identification information for identifying thetraffic corresponding to the sponsored data service and the servicerestriction information from the received access token, and gets theapproval message for the sponsored data service from the providernetwork in the embodiment above, the operations above may be performedin the opposite order, or may be modified. Particularly, if the validityof the access token received from the server cannot be identified, theUE may transmit the access token to the provider network to get thevalidity of the access token. Then, after approval for the sponsoreddata service, the UE may extract and store the service informationincluded in the access token for use.

The UE may transmit or receive the user plane data packets to or fromthe provider network at operation S2240.

When the user plane data packets are transmitted or received, the UE maydetermine whether the user plane data packets are included in thetraffic for the sponsored data service that has been stored before atoperation S2250. The UE may determine whether or not the user trafficcorresponds to the sponsored data service using the identificationinformation extracted from the access token. The UE may determinewhether or not the user traffic corresponds to the sponsored dataservice, based on whether the information included in the user planedata packet corresponds to the identification information. For example,the UE may identify whether or not the PDN connection or the EPS bearercontext (e.g., APN, QCI/ARP, and the like) included in the user planedata packets matches the identification information that is extracted(or stored) to thereby determine whether the user traffic corresponds tothe sponsored data service. In addition, the UE may identify whethersome of or all of the IP address/port or the URL of the user plane datapackets match the stored information to thereby determine whether theuser traffic corresponds to the sponsored data service.

If the transmitted and received user plane data packets correspond tothe sponsored data service traffic, the related user plane data packetsmay be managed as the traffic of the sponsored data service at operationS2260. For example, the UE may add the transmitted and received packetsto the amount of sponsored data based on the packet filters. Althoughnot described in the present disclosure, the initial value of the amountof sponsored data may be initiated or may be configured as a specificvalue when the sponsored data service is started. The amount of trafficmay be managed in various manners as well as the adding method of theamount of traffic. When the total amount of sponsored data is limited,the UE may calculate the remaining amount of sponsored data. This may beobtained by subtracting the volume of sponsored data that has beentransmitted and received until the present from the maximum amount ofsponsored data. The traffic may be managed periodically at apredetermined time, or irregularly whenever the user plane data packetsare created.

The UE may inform the user of the calculated volume of sponsored data(the amount of sponsored data) as information of the sponsored dataservice at operation S2270. The UE may output information on the amountof sponsored data service traffic. The information may be expressed asgraphs, or numbers (e.g., by a byte unit). In addition, when the totalamount of sponsored data is limited, the UE may inform the user of theremaining volume of sponsored data that has been calculated in theoperation above as information on the sponsored data service. Thisinformation may be expressed as graphs, or numbers (e.g., by a byteunit).

FIG. 23 illustrates an operation of a UE in the conditional sponsoreddata service according to an embodiment of the present disclosure.

Referring to FIG. 23, the UE provided with the sponsored data servicemay receive the access token for the sponsored data service from theserver or the network entity at operation S2310.

The UE may identify whether the data traffic transmitted and received bythe UE corresponds to the sponsored data service, based on theinformation include in the access token. For example, the UE may extractidentification information (e.g., a specific APN, a specific IP 5 tuple,a server URL, and the like) for identifying the traffic corresponding tothe sponsored data service, i.e., an IP flow, from the received accesstoken at operation S2320. The UE may store the extracted identificationinformation. The UE may perform an operation of separating the trafficcorresponding to the sponsored data service (that is, the traffic not tobe charged) among the traffic transmitted and received by the UE, basedon the extracted information. That is, the UE may identify the trafficcorresponding to the sponsored data service, based on the extractedinformation. In addition, the UE may extract service restrictioninformation (the maximum amount of data to which the sponsored dataservice is provided free of charge) from the access token. In addition,the UE may store the extracted service restriction information.

The UE may transmit a service request message including the receivedaccess token to the provider network at operation S2330. The UE may getthe approval for the sponsored data service by a response to themessage. The UE may trigger a timer for recording the time when thesponsored data service is provided to the user.

Although the UE extracts identification information for identifying thetraffic corresponding to the sponsored data service and the servicerestriction information from the received access token, and gets theapproval for the sponsored data service from the provider network in theembodiment above, the operations above may be performed in the oppositeorder, or may be modified. Particularly, if the validity of the accesstoken received from the server cannot be identified, the UE may transmitthe access token to the provider network to get the validity of theaccess token. Then, after approval for the sponsored data service, theUE may extract and store the service information included in the accesstoken for use, and at this time, the timer may be triggered together.The timer relates to the allowed time of the sponsored data service forthe UE. The sponsored data service may be provided free of charge if thetimer does not has expired.

The UE may identify whether or not the timer has expired at operationS2340.

If the timer has expired, the UE may inform the user that the sponsoreddata service has been terminated due to the expiration of the timer atoperation S2350.

In addition, the UE may selectively transmit a request message forending the sponsored data service to the provider network at operationS2360. In addition, the UE may receive a response message informing thatthe sponsored data service has ended.

If the timer has not expired, the UE may inform the user of informationon the remaining time for the sponsored data service at operation S2370.This information may be expressed by graphs or numbers (e.g., in hours,minutes, and seconds).

The various embodiments of FIGS. 21, 22, and 23 provide the method inwhich the UE extracts sponsored data service information (informationfor separating the traffic, the maximum volume, allowed time, and thelike) included in the access token received from the server to use. Thepresent disclosure is not limited thereto, and the UE may receive thesponsored data service information (information for separating thetraffic, the maximum volume, allowed time, and the like) from theprovider network instead of the access token for use.

Also the access token includes service information includes at least oneof information on allowed amount of the sponsored service andinformation on allowed time of the sponsored service, and the outputinformation includes at least one of information on remaining amount ofthe sponsored service based on the allowed amount and the calculatedamount, and information on remaining time of the sponsored service basedon the allowed time.

FIG. 24 illustrates a method by which a UE receives a sponsored dataservice information from a provider network for use according to anembodiment of the present description.

Referring to FIG. 24, the UE provided with the sponsored data servicemay receive the access token for the sponsored data service from theserver or the network entity at operation S2410.

The UE may transmit a service request message including the receivedaccess token to the provider network at operation S2420.

In response to the request, the UE may receive a message stating thatthe sponsored data service has been approved from the provider networkat operation S2430. The message may include the sponsored data serviceinformation (that has been used in the various embodiments of FIGS. 21to 23, more specifically, information for identifying the sponsored dataservice traffic, the maximum allowed volume of sponsored data, theapplication time of sponsored data service, and the like).

The UE may store the received information, and may perform the operation2440 (i.e., the operation of identifying the amount of sponsored data byseparating the sponsored data traffic, the operation of providinginformation to the user through limited time/volume, and the operationof making a request to the network for termination) of the variousembodiments in FIGS. 21 to 23. The UE may perform the operationsfollowing operation S2150 of FIG. 21, based on the sponsored dataservice information (information for separating the sponsored datatraffic). The UE may perform the operations following operation S2250 ofFIG. 22, based on the sponsored data service information (information onthe allowed volume of sponsored data). The UE may perform the operationsfollowing operation S2340 of FIG. 23, based on the sponsored dataservice information (information on the application time of sponsoreddata service).

The UE may make a request to the provider network for sponsored dataservice information (the volume of sponsored data traffic that has beentransmitted and received until the present, or the remainingvolume/time), and may receive the information to use without calculatingor measuring the same. The UE may receive a message in response to therequest message for the sponsored data service. The UE may output atleast one piece of information on the volume of transmitted/receivedsponsored data traffic, information on the volume of available sponsoreddata traffic, and information on the application time of sponsored dataservice, based on the information included the response message.

FIG. 25 illustrates a method by which the UE receives information on thesponsored data service in real time from the network for use.

Referring to FIG. 25, a UE 2510 may performs the sponsored data servicebased on method described various embodiments of the present disclosure.

Referring to FIG. 25, a UE 2510 may transmit an information requestmessage to figure out the current status of the sponsored data service(the volume of sponsored data traffic that has been transmitted andreceived until the present, the remaining volume, or the remaining time)to the provider network at operation S2501. The information requestmessage may include at least one of a user ID, a sponsored data serviceID, a request ID, a PLMN ID. The UE may request at least one piece ofinformation on the volume of transmitted/received sponsored datatraffic, information on the volume of available sponsored data traffic,and information on the application time of sponsored data service. Thereceiver of the request message may be an application function (AF)2530, more specifically, an enhanced proxy-call session control function(eP-CSCF) or an SES.

In addition, the creation and transmission of the request message by theUE 2510 may be triggered by the operation of identifying the statusinformation on the sponsored data service (i.e., executing applicationsfor identifying the sponsored data service in the UE, pressingbuttons/icons, or refreshing the status) by the user. Alternatively, theoperation may be automatically performed every predetermined timeconfigured in the UE 2510.

The message may be encoded using the HTTP protocol. Particularly, themessage may include information stating that the AF 2530 of the providernetwork provides the sponsored data service to the UE 2510 in responseto the request. Particularly, the information may be encoded using theSOAP protocol. In addition, the message may include at least one of auser ID, a sponsored data service ID, a request ID, a PLMN ID that hasbeen obtained when requesting the sponsored data service at thebeginning, or requested information (the amount of transmitted/receivedsponsored data until the present, the charge of the sponsored dataservice until the present, the remaining volume, the remaining time, andthe like). The charge of the sponsored data service until the presentmeans the charge that the sponsor (the third party) pays on behalf ofthe user through the sponsored data service.

The AF 2530 of the provider network that has received the requestmessage may search for the sponsored data service information (thecontext) of the UE 2510 using at least one of the user ID, the UE ID,the service ID, or the request ID at operation S2503.

The AF 2530 may transmit a response message to the UE 2510 at operationS2505. The message may be encoded using the HTTP protocol. Particularly,the message may include information stating that the AF 2530 of theprovider network provides the sponsored data service to the UE 2510 inresponse to the request. Particularly, the information may be encodedusing the SOAP protocol. In addition, the message may include thesponsored data service ID, the request ID that has been obtained whenrequesting the sponsored data service at the beginning, or requestedinformation (the amount of transmitted/received sponsored data until thepresent, the charge of the sponsored data service until the present, theremaining volume, the remaining time, and the like), which have beenpreviously received.

The UE 2510 may renew the sponsored data service information on the userusing the received message at operation S2507. In addition, the UE mayinform the user of the renewed information. This operation may includedisplaying a pop-up window for informing of the current status of thesponsored data service (e.g., the amount of transmitted/receivedsponsored data until the present, the charge of the sponsored dataservice until the present, the remaining volume, the remaining time, andthe like) on a screen, or refreshing a part of or all of a displayedimage on the screen of the UE, which informs of the status of thesponsored data service.

Although the AF 2530 transmits the response message in operation S2503in response to the request message transmitted by the UE 2510 inoperation S2501, the AF 2530 may be configured to automatically transmitthe information on the sponsored data service to the UE 2510 when apredetermined condition is satisfied. For example, period information,volume information of transmitted/received sponsored data service,sponsored charge information, or remaining volume information of thesponsored data service may be configured as a condition for triggeringthe transmission of information. The AF 2530 may transmit theinformation on the sponsored data service when the triggering conditionis satisfied regardless of the request of the UE 2510. At this time, thetriggering condition may be configured in the AF 2530 by the networkoperator, or may be configured according to a triggering condition setuprequest received from the UE 2510.

If one or more applications for the sponsored data service are installedin the UE, the UE may make a configuration for informing of the featuresof the sponsored data services.

FIG. 26 illustrates an example of displaying features of a sponsoreddata services in a UE according to an embodiment of the presentdisclosure.

Referring to FIG. 26, the UE may include an output unit. The output unitmay include various output means such as a display unit, a sound outputunit, a vibration output unit, and the like. The output unit may be usedfor outputting the information on the sponsored data service. Forexample, the output unit may be a screen 2600 of the UE. The displayunit of the UE may display sponsored data service applications (app).The display unit 2600 may display separate applications, a widget, orfunctions for showing information on the sponsored data serviceapplications.

The display unit 2600 may display information on each sponsored dataservice application. The display unit 2600 may display at least one ofthe applications 2610, 2620, 2630, and 2640 related to the sponsoreddata service. The applications may be displayed by text, images, oricons. The sponsored data service applications may be pre-loaded in theUE.

The display unit 2600 of the UE may display a plurality of applications.According to an embodiment of the present disclosure, the UE may displaythe sponsored data service applications to be distinct from generalapplications. For example, indicators showing the sponsored data serviceapplications may be displayed. In addition, the transparency or the sizeof the sponsored data service application may be different from thegeneral applications. In addition, the sponsored data serviceapplications may be displayed at a predetermined position. Thepredetermined position may be a position on the display unit, or apredetermined folder path. The information for separating the sponsoreddata service applications from the general applications may beconfigured by the UE or the network provider for providing the service.In addition, the sponsored data service applications and the generalapplications may be separated from each other using identificationinformation showing features of the sponsored data service applicationsas described below. The network entity for supporting the sponsored dataservice may transmit the identification-related information to the UE tothereby display the same. The UE may display the ID by the configurationin the UE or based on the identification-related information receivedfrom the network entity.

In addition, the display unit 2600 may display the identificationinformation 2613, 2623, 2633, and 2643 showing the features of thesponsored data service applications. The identification informationshowing the features of the applications may be always displayed on thedisplay unit 2600, or may be additionally displayed by a user input. Inthe case of displaying the identification information by the user input,the identification information may be displayed for a predeterminedamount of time, and then may disappear. The features of the sponsoreddata service application may include a rating of the sponsored dataservice, or current user grades of the sponsored data service.Information for identifying a rating of the sponsored data service oruser grades may be displayed according to the application features. Forexample, identification information may be displayed using colors,images, icons, text, and the like. In the case of colors, the rating ofthe sponsored data service or the grades may be displayed in differentcolors. For example, a high rating of service may be displayed in a goldcolor, and the next may be displayed in a silver color. Alternatively,the rating of the sponsored data service or the grades may be displayedby separate images or icons. For example, a high rating of service maybe displayed as “No. 1,” and the next may be displayed as “No. 2.” Thesponsored data service applications may be arranged according to thefeatures instead of displaying the identification information. Forexample, the sponsored data service applications may be displayed to bearranged according to the ratings or the grades on the display unit2600. The sponsored data service applications may be arrangedperiodically in a predetermined period, or may be arranged upon thereceipt of a user request. The UE may transmit an identificationinformation request message to the network entity for supporting thesponsored data service. The network entity that has received theidentification information request message may transmit a responsemessage including the identification information to the UE. The UE maydisplay the identification information on the features of the sponsoreddata service applications in colors, icons, images, or text, based onthe identification information received from the network entity.

Each sponsored data service application may have status information2615, 2625, 2635, and 2645. The status information may refer to theinformation showing the current service status for the user. The servicestatus may include at least one of the volume of sponsored data trafficthat has been transmitted and received until the present, the sponsoredcharge until the present, the remaining volume, or the remaining time,as described above. In addition, the status information may include thegrade, or the service level/class information, which have been obtainedby the user in the corresponding sponsored data service. Suchinformation may be expressed as numbers, text, graphs, images, or icons.The status information may be always displayed on the display unit 2600,or may be additionally displayed by the user input. In the case ofdisplaying the status information by the user input, the statusinformation may be displayed for a predetermined amount of time, andthen may disappear. In addition, the status information may be displayedto be enlarged by the user input. For example, when at least oneapplication is selected from among a plurality of sponsored data serviceapplications, the status information corresponding to the selectedapplication may be displayed to be enlarged, and the detailedinformation thereof, which has not been displayed due to the limitationof space, may be additionally displayed. The status information mayprovide statistical information on the use of the sponsored data serviceuntil the present as well as the current status information on thesponsored data service used by the UE. In order to display such statusinformation, the UE may receive the status information from the networkentity of the sponsored data service.

In the various embodiments of the present disclosure, although theaccess token is transmitted from the server (the web server or WWSF) tothe UE, the UE may create the access token itself. That is, theoperation of receiving the access token from the server may be replacedwith the operation of obtaining information (element of the access tokenset forth above) for creating the access token, and afterwards, the UEmay create the access token to be thereby transmitted to the providernetwork for the sponsored data service.

Although various embodiments of the present disclosure have been shownand described in this specification and the drawings, they are used ingeneral sense in order to easily explain technical contents of thepresent disclosure, and to help comprehension of the present disclosure,and are not intended to limit the scope of the present disclosure. It isobvious to those skilled in the art to which the present disclosurepertains that other modified embodiments on the basis of the spirits ofthe present disclosure besides the embodiments disclosed herein may becarried out.

While the present disclosure has been shown and described with referenceto various embodiments thereof, it will be understood by those skilledin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the present disclosure asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A terminal in a wireless communication system,the terminal comprising: a transceiver configured to transmit andreceive a signal; and at least one processor configured to: transmit apublic land mobile network identifier (PLMN ID) for a sponsored service,to a first server, receive a token related to the sponsored service fromthe first server, transmit a sponsored service request message based onthe token, to a second server, receive authentication information fromthe second server, and display at least one of information on anidentified amount of at least one of a packet transmission or a packetreception for the sponsored service, or information on remaining amountfor the sponsored service based on allowed amount for the sponsoredservice and the identified amount.
 2. The terminal of claim 1, whereinthe at least one processor is further configured to configure a packetfilter for the sponsored service, and wherein the amount of the at leastone of the packet transmission or the packet reception for the sponsoredservice is identified based on the packet filter.
 3. The terminal ofclaim 1, wherein the at least one processor is further configured toidentify the amount of at least one of the packet transmission or apacket reception for the sponsored service.
 4. The terminal of claim 1,wherein the token includes at least one of the allowed amount for thesponsored service or allowed time for the sponsored service.
 5. Theterminal of claim 1, wherein the at least one processor is furtherconfigured to display at least one of information on identified time ofthe at least one of the packet transmission or the packet reception orinformation on remaining time for the sponsored service based on allowedtime for the sponsored service and identified time.
 6. The terminal ofclaim 1, wherein the at least one processor is further configured todisplay at least two applications related to each of at least twosponsored services, and wherein the application includes statusinformation corresponding to the each of the sponsored services.
 7. Theterminal of claim 1, wherein the sponsored service is a specific servicethat a service provider pays charge of a traffic between the terminaland the service provider to a network operator.
 8. A server in awireless communication system, the server comprising: a transceiverconfigured to transmit and receive a packet; and at least one processorconfigured to: store a token related to a sponsored service, the tokencorresponding to a public land mobile network identifier (PLMN ID) of anetwork operator, receive a sponsored service request message from aterminal, determine whether the terminal is authorized to use thesponsored service based on the token and the sponsored service requestmessage, and transmit authentication information indicating whether theterminal is authorized to use the sponsored service to the terminal,wherein an amount of at least one of a packet transmission or a packetreception for the sponsored service is identified by the terminal, andwherein at least one of information on the identified amount orinformation on remaining amount for the sponsored service based onallowed amount for the sponsored service and the identified amount isdisplayed by the terminal.
 9. The server of claim 8, wherein thesponsored service is a specific service that the service provider payscharge for a traffic between the terminal and a service provider to thenetwork operator.
 10. The server of claim 8, wherein the token includesat least one of the allowed amount for the sponsored service or allowedtime for the sponsored service.
 11. A method by a terminal in a wirelesscommunication system, the method comprising: transmitting a public landmobile network identifier (PLMN ID) for a sponsored service, to a firstserver; receiving a token related to the sponsored service from thefirst server; transmitting a sponsored service request message based onthe token, to a second server; receiving authentication information fromthe second server; and displaying at least one of information on anidentified amount or information on remaining amount for the sponsoredservice based on allowed amount for the sponsored service and theidentified amount.
 12. The method of claim 11, further comprising:configuring a packet filter for the sponsored service, wherein theamount of the at least one of the packet transmission or the packetreception for the sponsored service is identified based on the packetfilter.
 13. The method of claim 11, further comprising identifying theamount of at least one of the packet transmission or a packet receptionfor the sponsored service.
 14. The method of claim 11, wherein the tokenincludes at least one of the allowed amount for the sponsored service orallowed time for the sponsored service.
 15. The method of claim 11,further comprising: displaying at least one of information on identifiedtime of the at least one of the packet transmission or the packetreception or information on remaining time for the sponsored servicebased on allowed time for the sponsored service and identified time. 16.The method of claim 11, further comprising: displaying at least twoapplications related to each of at least two sponsored services, whereinthe application includes status information corresponding to the each ofthe sponsored services.
 17. The method of claim 11, wherein thesponsored service is a specific service that a service provider payscharge of a traffic between the terminal and the service provider to anetwork operator.
 18. A method by a server in a wireless communicationsystem, the method comprising: storing a token related to a sponsoredservice, the token corresponding to a public land mobile networkidentifier (PLMN ID) of a network operator; receiving a sponsoredservice request message from a terminal; determining whether theterminal is authorized to use the sponsored service based on the tokenand the sponsored service request message; and transmittingauthentication information indicating whether the terminal is authorizedto use the sponsored service to the terminal, wherein an amount of atleast one of a packet transmission or a packet reception for thesponsored service is identified by the terminal, and wherein at leastone of information on the identified amount or information on remainingamount for the sponsored service based on allowed amount for thesponsored service and the identified amount is displayed by theterminal.
 19. The method of claim 18, wherein the sponsored service is aspecific service that the service provider pays a charge of for trafficbetween the terminal and the service provider to the network operator.20. The method of claim 18, wherein the token includes at least one ofthe allowed amount for the sponsored service or allowed time for thesponsored service.